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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the auth requirement (`full_access` key) and the underlying HTTP endpoint, which are useful beyond the annotations, but says nothing about pagination behavior, result ordering, or volume beyond what the schema implies.

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 short sentences with no filler, and the auth constraint is stated up front. The trailing parenthetical '(operationId `listBroadcasts`, Broadcasts)' adds little for an agent and is slightly noisy, but the overall size is appropriate.

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 100% schema coverage and annotations carrying the safety profile, and no output schema required, the essentials are present. However, for a paginated list tool the description never mentions that results are paginated or how the page tokens work, leaving the agent to infer this from parameter names alone.

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%, and all three parameters (after, limit, before) are fully documented in the schema including the mutual-exclusion rule between after and before. The description contributes nothing on parameters, 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 description restates the tool name almost verbatim ('List broadcasts') rather than adding a distinct verb+resource framing, and does not differentiate this from sibling list_* tools or from get_broadcast. It does add the concrete endpoint and operationId, which confirms the resource being listed, but the semantic content is largely tautological.

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 only guidance is the prerequisite that a `full_access` API key is required, which is genuinely useful. There is no indication of when to choose this tool over get_broadcast for a single record, or over the other list_* siblings, and no exclusions or context are given.

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