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

readOnlyHint=true already tells the agent this is a safe read, so the description's added value is the return-content hint ('including its status and summary'), which is genuinely useful because no output schema exists. It also names the underlying API endpoint. It does not mention failure behavior (e.g., unknown id), but the annotation covers the main safety question.

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, front-loaded with the action and scope, with no filler. The trailing API endpoint line is mildly redundant with the tool name but compact enough not to hurt.

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 with full schema coverage and annotations covering safety, most of the burden is met, and the partial return-value note compensates for the absent output schema. The remaining gap is disambiguation from get_broadcast_details, which the description never addresses.

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 the single parameter is documented as 'The BroadcastID.' with a string/number union. The description only restates 'by id' and adds no format, source, or constraint detail beyond the schema, so the 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?

States a specific verb and resource ('Fetch a single broadcast by id') and scopes it to one record, which distinguishes it from the plural sibling list_broadcasts. However, it does nothing to distinguish itself from the very similar get_broadcast_details sibling, so an agent cannot be sure which of the two to pick from the text alone.

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 usage cue is implicit: you need an id, so this is a lookup. There is no statement of when to prefer this tool over get_broadcast_details or list_broadcasts, and no exclusions or prerequisites given. For a family with two near-identical 'get broadcast' siblings, that omission matters.

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