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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is an irreversible-feeling mutation. The description adds nothing beyond that — no statement about permanence, cascading effects on requirements/stories/subsystems, or required permissions. Restating "delete" contributes no behavioral context.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity shades into under-specification rather than economy — the sentence is short because nothing was explained, not because everything was squeezed in.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. But for a destructive, presumably irreversible project deletion, the definition omits cascading impact, permission requirements, and any pointer to recovery tools — meaningful missing context for an agent deciding whether to call it.

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 description coverage is 100% and there is only one parameter (project_id, a UUID), so the schema fully documents the input. The description adds no format or sourcing detail, which is the expected baseline 3 when the schema does all the work.

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?

"Delete a project" states a specific verb and resource, so the agent immediately knows this removes a project rather than reading or updating one. It does not, however, contrast itself with adjacent siblings like projects_undo, projects_patch, or restore_project_snapshot, which are the tools most likely to be confused with a delete.

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?

There is no guidance about when deletion is appropriate, whether it can be undone, or that projects_undo / restore_project_snapshot exist as alternatives. For a destructive operation in a toolset full of sibling project mutations, this absence is a real gap.

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