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

No annotations are provided, so the description carries the behavioral burden. It discloses the non-destructive nature and the preview output, but does not cover permissions, invalid-id handling, or other operational constraints.

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?

Four short sentences with 'Dry run' front-loaded and no wasted text. The safety note and sibling call-to-action each earn their 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 a simple one-parameter preview tool with no output schema and no annotations, the description explains what will be shown and that nothing is deleted. The main gap is that it does not explain the id parameter.

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?

The only parameter is a required UUID with 0% schema description coverage, and the description never explicitly explains that id identifies the SDR process/search. 'The process' is only an implicit hint.

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?

The description clearly states this is a dry-run preview for deleting an SDR process, names the information shown (process, lost contacts/signals, campaign status), and distinguishes it from the destructive sibling sdr_delete_search.

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 explicitly says to call it before sdr_delete_search, which tells the agent both the purpose and the relevant alternative. 'Dry run' and 'Nothing is deleted' further clarify when this tool is appropriate.

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