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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about what data is included in the response, but it does not address not-found behavior, authentication needs, or how the broadcast is identified.

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?

A single front-loaded sentence with no redundant wording. Every clause adds information about the returned resource, and there is no 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 simple single-resource read tool, the description gives a reasonable picture of the returned fields and is consistent with the read-only annotation. It falls short by not explaining the required broadcast_id, limiting an agent's ability to invoke the tool correctly without inspecting the schema.

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?

There is exactly one parameter, broadcast_id, and the schema has 0% description coverage. The description refers only to 'a broadcast' and never mentions the identifier, its format, or where to obtain it, so it does not compensate for the undocumented parameter.

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 verb ('Read') and resource ('a broadcast') and enumerates the data returned (audience, content, merge tags, status, schedule). It is clearly distinct from the similarly named list_broadcasts by being a singular fetch, though it does not explicitly name that sibling.

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 verb 'Read' and the singular resource imply fetching one broadcast by identifier, which is adequate implied usage. However, there is no explicit guidance on when to use this versus list_broadcasts, get_broadcast_stats, or get_broadcast_readiness.

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