| @@ -8,20 +8,13 @@ | ||
| 8 | 8 | |
| 9 | 9 | defined('ABSPATH') || exit; |
| 10 | 10 | |
| 11 | 11 | /** |
| 12 | - * MCP prompts — worked procedures the operator can invoke by name. | |
| 12 | + * MCP prompts: step-by-step procedures the operator can run by name. | |
| 13 | 13 | * |
| 14 | - * Prompts are the right home for anything that would otherwise have been | |
| 15 | - * crammed into a tool description, because a prompt costs almost nothing until | |
| 16 | - * someone runs it: clients list its name, description and arguments, and fetch | |
| 17 | - * the body only on invocation. That makes them cheap in exactly the currency | |
| 18 | - * this design spends everywhere else — resident context. | |
| 19 | - * | |
| 20 | - * So each one here is a procedure rather than a paragraph: which tools to call, | |
| 21 | - * in what order, and what to do when they disagree. The three shipped are the | |
| 22 | - * three tasks that came up over and over while building the tools, and they | |
| 23 | - * double as the eval fixtures in §15 of the spec. | |
| 14 | + * Clients fetch a prompt's body only when it runs, so long guidance lives here | |
| 15 | + * rather than in tool descriptions. These double as the eval fixtures in §15 | |
| 16 | + * of the spec. | |
| 24 | 17 | * |
| 25 | 18 | * @since 2.2.6 |
| 26 | 19 | */ |
| 27 | 20 | class BookingPrompts |
