Delete blueprint

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

Annotations indicate destructiveHint=true, but the description adds significant behavioral context: the first call is non-destructive, the two-step confirmation process, and that servers are unaffected. No contradiction with annotations.

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 concise sentences with the action front-loaded. Every sentence adds value: verb+resource, safety assurance, two-step process, side effects. No unnecessary words.

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?

The description covers key aspects: what it does, how it works, safety, and side effects. Without an output schema, it adequately explains the return behavior (preview+token). Minor omission: not specifying what the 'preview' contains, but overall complete for a deletion tool.

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 has 3 parameters but only 33% coverage. The description indirectly explains the dry_run and confirm_token parameters through the workflow description, adding meaning beyond the schema. However, it does not explicitly name dry_run, leaving some ambiguity.

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 'Delete a saved blueprint' with a specific verb and resource. It distinguishes from sibling delete tools by mentioning 'from the local store' and the preview/confirm pattern, which is unique among delete 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?

The description provides clear guidance on how to use the tool (first call returns preview+token, second call deletes) and mentions that servers built from the blueprint are untouched. However, it does not explicitly state when not to use it or list alternative tools for similar purposes.

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