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

Annotations already declare destructiveHint=true, but the description adds substantial context beyond them: irreversibility, the exact blast radius, that the platform deletes in the background after immediate disappearance from list_projects, that the confirm_name mismatch guard aborts with nothing deleted, and that a read-write token is required. This is precisely the extra behavioral context the annotations cannot carry.

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?

Front-loaded with 'Destructive and irreversible' so the risk lands first, then scope, then the confirmation contract, then eligibility. Every sentence carries distinct information; the confirm_name sentence slightly overlaps the schema but reinforces the abort behavior.

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 2-parameter destructive tool with an output schema and full annotation coverage, nothing an agent needs is missing: risk, blast radius, async side effects, the abort condition, auth requirements, and the sibling alternative 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 both parameters are already documented, and the description mostly restates confirm_name. It does add marginal value by framing the mismatch guard as an atomic failure ('nothing is deleted') and tying project_id/confirm_name to list_projects as the source of truth, but it offers no format or syntax detail beyond the 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?

States a specific verb (deletes) and resource (a WHOLE project, by project_id) and enumerates exactly what goes with it: commits, deployments, hosts, volumes, restore points, managed database, bucket, and source repository. It explicitly contrasts with the sibling delete_commit, so an agent can distinguish destructive-scope variants without opening schemas.

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?

Gives an affirmative condition (a project the user asked for by name, e.g. a test app or one made by mistake) and an explicit exclusion (never as cleanup the user did not ask for). It names the alternative for the narrower case: delete_commit, to remove one commit and keep the project.

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