Delete a post template

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

Annotations already mark destructiveHint: true, but the description adds crucial behavioral detail: the deletion is permanent, requires explicit confirmation, and does not affect posts already created from the template. This goes well beyond the structured annotation and gives an agent a clear model of the tool's side effects.

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?

Three short sentences, each earning its place: the primary action, the critical safety requirement, and the important side-effect boundary. Key information is front-loaded and there is no fluff.

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 destructive action with three documented parameters and a destructive annotation, the description covers everything an agent needs: what it deletes, that it is permanent, how to authorize it, and what it does not affect. No output schema exists, so describing return values is unnecessary.

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 input schema covers 100% of parameters with descriptions, including the confirm requirement and the id source. The tool description reinforces the confirm parameter's behavior but does not add additional parameter-level meaning beyond what the schema already provides. 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 opens with a specific verb and resource: 'Delete a saved template.' This clearly distinguishes it from sibling tools like delete_draft and delete_note, and the additional context about permanence and unaffected posts further sharpens the tool's purpose.

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?

The description clearly states the context in which the tool is used: deleting a saved template. It also provides an important usage prerequisite by warning that the action refuses to run without confirm: true. It does not explicitly name alternatives, but the resource type makes the intended use unambiguous.

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