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

With no annotations at all, the description carries the full burden and does disclose the two most important traits: the deletion is permanent/irreversible and it requires prior preview plus user approval. It stops short of saying what else is removed (attachments, history) or what happens on an invalid lead_id.

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 short sentences with zero padding, and the destructive nature is front-loaded before the precondition. Every clause earns its place.

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 annotation-free destructive tool with no output schema and two required params, the description covers the critical safety workflow. The remaining gaps — where to source lead_id, cascade effects of deletion, and error behavior — are real but secondary.

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 coverage is only 50%: `id` is documented in the schema but `lead_id` has no description anywhere. The description adds no parameter-level detail and does not compensate — it never explains that lead_id identifies the narrator lead (nor where to obtain it, e.g. list_narrator_leads).

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 ('delete') and resource ('presentation lead'), with 'Permanently' reinforcing the scope. It distinguishes itself from update_narrator_lead and preview_delete_narrator_lead by name, though the mild mismatch between 'presentation lead' and 'narrator lead' leaves slight ambiguity about which entity type is targeted.

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?

Explicitly names the required prerequisite (preview_delete_narrator_lead) and the human-in-the-loop condition (explicit user approval). An agent knows exactly what must happen before calling this, and the prerequisite implicitly excludes direct invocation.

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