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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description contributes the URL shape and the framing that results describe delivery/engagement outcomes, but says nothing about pagination limits or result volume, which matters for a potentially large recipient set.

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 sentences plus an endpoint reference, front-loaded with the outcome-oriented framing before the technical path. The enumeration of kind values partially duplicates the schema enum and costs some space, keeping it just short of ideal.

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?

With no output schema, the description usefully signals that records include delivery and engagement status, which tells the agent what comes back. Pagination mechanics are left entirely to the schema, and there is no note on result size, but for a filtered list tool this is close to sufficient.

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 100%, including the enum for kind, page/limit defaults and the next_page continuation hint, so the schema carries the parameter burden. The description restates the kind values and mentions group filtering without adding format or default detail beyond the schema, so baseline 3 applies.

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 opening phrase 'Who received a mailing and what happened' states the resource and the shape of the answer, and the endpoint 'GET /mailings/{id}/recipients[/{kind}]' pins down the operation precisely. It does not differentiate itself from near-neighbours like cyberimpact_list_bounced_members or cyberimpact_list_unsubscribed_members, so an agent must infer that this one is scoped to a single mailing.

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?

'Optionally only recipients from one group' gives one scoping hint, and the enumerated kinds imply the segmentation use case. However, there is no explicit when-to-use guidance and no statement of when to prefer cyberimpact_get_mailing or the sibling bounce/unsubscribe listers instead.

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