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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger profile is covered by structured data. The word "Permanently" adds a small amount of value by reinforcing irreversibility, but the description says nothing about what else is destroyed (work items, graphs, baselines), whether the deletion cascades, or whether the caller must be an owner.

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?

One sentence, front-loaded with the verb and qualified with the permanence warning. Nothing is wasted and nothing is buried.

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 an irreversible, destructive operation on a top-level container, the definition omits the information an agent most needs before invoking: what happens to dependent objects and whether authorization is required. The annotations cover the safety flag, but the blast radius of deleting a project is left entirely unexplained.

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?

There is a single required parameter with 100% schema description coverage, so the schema carries the parameter documentation. The description adds no meaning beyond it, which is the expected baseline when coverage is complete.

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?

"Permanently delete a project" gives a specific verb (delete), a specific resource (project), and a scope qualifier (permanent). This clearly distinguishes it from delete_concept and delete_relation, though it does not explicitly contrast with sibling lifecycle tools like leave_project or update_project, which is the main gap.

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 on when to use this instead of leave_project (which presumably removes membership without destroying the project) or update_project. No prerequisites, permissions, or confirmation requirements are stated.

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