Delete a saved playbook

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description contradicts the annotations: it states 'Delete one of your saved playbooks' implying destructive behavior, while annotations declare destructiveHint=false. This is a clear contradiction. The added context about bundled playbooks is useful but cannot offset the inconsistency.

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 two concise sentences, with the purpose front-loaded. The second sentence adds essential nuance about bundled playbooks. No wasted words, though it could be slightly more structured.

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?

For a simple delete tool with one parameter and no output schema, it covers the primary action and a key caveat. However, the contradiction with annotations and lack of error handling or result information make it incomplete. A 3 is fair given the simplicity.

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 covers the single parameter 'name' with a description, and the tool description adds little beyond that, only clarifying that it refers to a saved skill. With 100% schema coverage, baseline 3 is appropriate.

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?

The description clearly states the action (delete) and the resource (saved playbooks). It adds a relevant nuance about bundled playbooks, which distinguishes it from generic delete tools, though it does not explicitly separate it from sibling delete_* tools. The verb+resource is specific enough.

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 on when to use this tool versus alternatives. It does not mention any sibling tools or conditions that would select this over others (e.g., delete_content, delete_term). The caveat about bundled playbooks is a constraint, not a usage guideline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.