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

No annotations exist, so the description carries the burden, and it does the most important part: 'Nothing is deleted' makes the read-only nature unambiguous and the sequencing sentence encodes a confirmation-workflow requirement. It stops short of describing what the preview actually contains or whether it is guaranteed to still be current at delete time.

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?

Three very short sentences, front-loaded with the purpose and the safety guarantee. No filler; every clause adds routing or safety information.

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 preview tool with no output schema, the essential information (safe, read-only, must precede the delete) is present. It would be stronger if it stated what the preview returns or that it validates the lead exists, but nothing critical is missing for correct invocation.

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% and lead_id has no description at all, yet the description never mentions either parameter. It does not clarify that id is the agent UUID sourced from list_agents or that lead_id must identify an existing narrator lead, so it fails to compensate for the coverage gap.

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?

Names a specific verb and resource ('Show the lead that would be deleted') and immediately distinguishes itself from the mutating sibling delete_narrator_lead. An agent can tell exactly what this does without opening the schema.

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?

Explicit sequencing guidance: 'Call first and show the user before delete_narrator_lead.' It names both the timing (first) and the required intermediate step (show the user), so there is no ambiguity about when this is used instead of the delete tool.

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