Remove an existing prompt book configuration using its ID to maintain an organized set of prompt collections.
Remove a prompt book configuration
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the prompt book to remove |
Changes observed during successful MCP inspections.
v1.0.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Remove' implies destruction, but the description does not state whether removal is permanent, whether it affects associated prompts, or whether any confirmation is needed. This is opaque for a destructive tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short phrase with no filler, which is structurally clean. However, it is under-specified for a deletion operation and provides no behavioral or usage context that would help an agent use it confidently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and only one parameter, the description is the only source of context. It does not explain what happens when the config is removed, whether the operation is reversible, or what error behavior to expect. This is insufficient for a destructive tool with no additional metadata.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema documentation coverage is 100%, with the id parameter described as 'ID of the prompt book to remove'. The description adds no additional semantic value beyond the schema, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states the specific action 'Remove' and resource 'prompt book configuration', which distinguishes it from siblings like create, rename, or list. It is clear about what the tool does, though it does not explicitly contrast it with the other prompt-book tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool instead of alternatives such as rename_prompt_book or deactivate/activate. There is no mention of prerequisites, edge cases, or what qualifies as a prompt book configuration. Usage is only implied by the verb and resource.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.