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

readOnlyHint=true already covers the safety profile, and the description adds genuinely useful context about the result shape (who was reached, delivery status). However, it says nothing about volume, pagination, or whether details are available only after sending completes — meaningful gaps for a per-contact result set that can be large.

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 tight sentences: the purpose and return contents come first, followed by the concrete API endpoint. No redundancy or filler.

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 one-parameter read-only tool with no output schema, the description compensates by naming what the response contains (per-contact reach and delivery status). Pagination/limits and freshness of results remain unspecified, so it falls just short of 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?

Single parameter with 100% schema description coverage, so the schema already documents the BroadcastID; the description only echoes it via the REST path. Baseline 3 is appropriate since nothing beyond the schema is added.

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 (Fetch) and resource (per-contact delivery details/results for a broadcast), with parenthetical scope clarification of what the data contains. It is clearly distinguishable from a broadcast-summary fetch, though it never explicitly names the sibling get_broadcast to contrast scope.

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?

Usage is only implied: an agent can infer this is for inspecting individual delivery outcomes of an already-sent broadcast, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., get_broadcast for summary vs this for per-recipient detail).

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