delete_blueprint

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

Since no annotations are provided, the description fully carries the burden of behavioral disclosure. It clearly states the destructive and irreversible nature of the tool, which is critical for an AI agent to understand before invocation.

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 extremely concise: one line for purpose and a warning, plus a single parameter doc line. No unnecessary text, front-loaded with the critical irreversible warning.

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 tool with one parameter and an output schema (implied), the description is complete. It covers purpose, usage guidance, behavioral transparency, and parameter meaning. No gaps given the tool's 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 description mentions 'blueprint_id: Blueprint UUID', adding context that the parameter is a UUID. Given that schema description coverage is 0%, this helps clarify the parameter meaning beyond the schema, though it could provide more detail like format or example.

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' on the 'blueprint' resource. It is unambiguous and distinct from sibling tools like 'create_blueprint' or 'update_blueprint'.

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?

Explicitly warns that the operation is irreversible and advises confirmation before calling. This provides clear guidance on when and how to use the tool, distinguishing it from non-destructive operations.

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