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 genuinely new context the annotations do not: deletion is permanent and cascades to connected social accounts, OAuth grants, media references, and posts — exactly what an agent needs to gauge blast radius before calling.

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; the permanence and cascade details arrive immediately rather than being 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 a destructive single-parameter tool with full annotation coverage and no output schema, the description covers permanence and cascade targets, which is the critical missing piece elsewhere. Minor gap: no note on auth/permission requirements or error behavior when the project is missing.

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?

Only one parameter (projectId) with 100% schema description coverage, so the schema carries the semantics. The description adds scope ('one project') but no identifier format or provenance guidance, which is the expected baseline.

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 deletes one project and its related data'. The cascade scope ('one project and its related data') makes it distinguishable from media_delete, posts_delete, and social_accounts_delete, though it never explicitly contrasts with those siblings.

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?

The word 'Permanently' implies this is irreversible and should be used with care, but there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g., deleting a single social account via social_accounts_delete instead). 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.