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

With no annotations, the description carries the behavioral burden and does well: it discloses that this is non-mutating ('Dry run'), that it validates each id against the search, and that results are grouped counts. It does not detail error behavior or permission requirements, but the core behavior is transparent.

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?

The description is a single efficient sentence with the core concept front-loaded. Every clause adds useful information: dry-run nature, validation against the search, and grouped counting.

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 annotations or output schema, the description covers the essential call semantics: it is a dry run, ids must belong to the search, and results are counted by group. It could say more about invalid-id handling or the exact result shape, but the core is complete.

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 0%, so the description must add meaning. It implies that 'ids' are checked against the 'search_id' search and that multiple ids are involved, but it does not fully annotate both parameters or their constraints beyond that relationship.

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 states a specific operation — a dry run of a multi-select delete — and adds what the preview checks: every id belongs to the search and counts by group. This distinguishes it from the actual bulk delete and from single-person previews, though it does not explicitly name 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 phrase 'Dry run' implies this should be used before a real multi-select delete, but the description never explicitly says when to use it, when not to use it, or that sdr_bulk_delete_people is the follow-up action. Usage is clear enough by implication but not spelled out.

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