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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond them by naming exactly what is destroyed in the cascade (answers, contributors, generations, project orders), which an agent cannot derive from the schema; it stops short of stating permission requirements or recoverability guarantees.

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 the irreversible action and its blast radius; every clause earns its place and there is no filler.

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 two-parameter destructive tool with no output schema and strong annotations, the description covers the crucial unknown (cascade scope) and the irreversibility implied by 'Permanently'. It is nearly complete, missing only routing guidance against sibling tools.

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 only 50%: confirmPermanentDeletion is documented in-schema, but projectId has no description. The tool description says nothing about either parameter, so it fails to compensate for the undocumented half, and the required explicit-confirmation semantics live entirely in the schema.

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 life-story project') and immediately enumerates the cascade scope (answers, contributors, generations, project orders). This lets an agent separate it from softer siblings like close_life_project_contributions or the narrower delete_story.

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 and no mention of alternatives, despite an obvious near-neighbor in close_life_project_contributions (a likely non-destructive counterpart) and delete_story. The agent must infer that this is the hard-delete path purely from the word 'Permanently'.

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