delete_project

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

No annotations provided, so description carries full burden. It details the full destructive cascade, status change, and removal from key store, emphasizing irreversibility.

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?

Description is focused and front-loaded with key info ('immediately and irreversibly delete'). Each sentence adds value, though slightly verbose with the list of actions. Still efficient.

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?

Given one parameter, no output schema, and no annotations, the description is remarkably complete: scope, consequences, behavioral traits, and when to use alternatives are all covered.

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?

Schema already covers `project_id` with 'irreversible cascade purge'. Description adds context about what that entails, but schema coverage is 100%, so baseline 3; description adds value beyond schema.

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 identifies the action as immediate and irreversible deletion of a project, listing specific destructive steps (drop schema, delete Lambda, etc.) and distinguishes from the lease-expiry grace window and `set_tier` sibling.

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`). Also clarifies it's distinct from automatic lease-expiry.

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