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

Annotations already declare readOnlyHint=true so the safety profile is covered. The description adds the return payload hint (status and summary) and the underlying REST endpoint, which is modest added context, but it says nothing about error behavior for a missing id or whether extra detail requires the sibling tool.

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 purpose and with no filler. The endpoint mapping in the second sentence is marginally redundant but still useful for agents reasoning about the underlying API.

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 a single required parameter and no output schema, the description does partially compensate by naming the returned fields. Still missing is any differentiation from get_broadcast_details and any indication of how thin this response is relative to that sibling, leaving a real routing gap.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents 'id' as the BroadcastID with its string/number union. The description's phrase 'by id' adds no syntax, format, or sourcing detail beyond that, 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?

States a specific verb and resource ('Fetch a single broadcast by id') and names the returned content ('status and summary'), so the operation is unambiguous. However, it never distinguishes itself from the sibling get_broadcast_details, which reads very similarly, so an agent cannot route between them from the description 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?

There is no statement of when to use this tool versus alternatives, and the sibling set contains both get_broadcast_details and list_broadcasts, which are the obvious competing choices. The description gives no selection criteria, exclusions, or prerequisites.

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