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

Annotations only supply readOnlyHint=false, so the description carries the real burden and does so well: it discloses the 7-day slug quarantine, immediate re-use by the same account, and a 409 for other accounts during the window. It does not state irreversibility or that project data is unrecoverable, leaving a small gap.

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?

Two tight sentences, front-loaded with the action and followed by the consequence. Every clause (quarantine duration, immediate re-use, 409 for others) carries information an agent would otherwise have to guess.

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 single-param destructive tool with no output schema, the description covers the operation and its downstream effects well. It omits authorization requirements and whether the deletion is reversible, which would be the remaining useful additions.

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?

One parameter ('project') with 0% schema description coverage. The description's reference to 'its slug' hints that the identifier is a slug rather than an ID or display name, but it never states the expected format or that the parameter is effectively required despite schema saying otherwise.

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 compound verb (stop and delete) and the exact resource (a project). The 'stop and delete' phrasing distinguishes it from the sibling stop_project, which only halts execution without destroying the project.

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 when-to-use guidance, no mention of the alternative stop_project for reversible shutdowns, and no stated prerequisites such as required permissions or confirmation. The agent must infer that this is the terminal, destructive option.

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