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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: the history is destroyed and cannot be restored, and it explains the confirm_name guard's failure mode ('otherwise nothing is deleted').

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 tightly packed clauses with the irreversible scope constraint front-loaded, followed by the when-to-use restriction and the guard parameter. No filler sentences; every clause carries operative information.

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, two-parameter tool with an output schema absent and annotations covering the safety hints, nothing an agent needs to invoke it correctly is missing: scope, irreversibility, precondition, and the confirm_name contract are all present.

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 coverage is 100%, so the baseline is 3. The description goes further by clarifying that confirm_name must be the exact current name sourced from list_projects and that a mismatch silently aborts the deletion, adding meaning not present in the schema's terse property descriptions.

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?

States a specific verb (Deletes) and resource (project) with precise scope: ONE, permanently, including its history. An agent can distinguish this from create_project, duplicate_project, and restore_version without opening any schema.

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 limits use to the case where the user asks to delete this very project, and explicitly excludes autonomous cleanup ('never to tidy up on your own') and bulk deletion ('never for several at once'). It also routes the agent to list_projects for obtaining the exact name.

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