delete_project

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

No annotations provided, so description bears full burden. It thoroughly enumerates the destructive cascade (drop tenant schema, delete Lambda functions, release subdomains, etc.) and clearly labels the action as irreversible. No hidden behaviors.

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 sentences, compact yet comprehensive. Front-loaded with the core action and key implications. Every sentence adds value without repetition.

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?

Complete for a delete tool with one parameter and no output schema. Covers what happens, irreversibility, distinction from grace window, and recovery alternative. No missing information.

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?

Only one parameter with 100% schema coverage. Description adds context about irreversibility and cascade, but the schema already describes 'project ID to delete (irreversible cascade purge)' which is consistent. Minimal additional value, but sufficient.

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 explicitly states 'delete a project' and details the irreversible destructive cascade, clearly distinguishing this from the automatic lease-expiry grace window. It leaves no ambiguity about the action.

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 states when to use (explicit purge) and when not to (for recovery from missed renewal, use set_tier instead). Provides clear alternative and context.

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