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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond them: permanent irreversibility and the two authorization requirements (connection-time scope plus owner role). It doesn't say what happens to dependent resources, which keeps it from a 5.

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 sentences, front-loaded with the action and its permanence, then the permission requirements. No filler and nothing redundant with the annotations.

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, no-output-schema tool, the description covers permanence and auth but leaves gaps: no cascading-effect disclosure (what is destroyed alongside the project) and no idempotency_key semantics. Adequate as a minimum, notably incomplete for an irreversible operation.

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 0%, so the description carries the full burden for both parameters and explains neither. project_id is reasonably self-evident from the name, but idempotency_key (8-200 chars, how retries are deduplicated) is entirely undefined despite the tool being retry-safe.

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 and resource ('Permanently delete a project'), and the adverb 'permanently' disambiguates from a soft-archive/update operation. It doesn't explicitly name a sibling, but no other sibling deletes a project, so the agent can route to it unambiguously.

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?

It states prerequisites (hypotize:delete scope granted at connection time, owner role), which tells the agent when the call will be permitted. However, it gives no guidance on alternatives or when deletion is preferable to hypotize_project_update or archiving, so usage is only implied.

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