Get Broadcast

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

The description is consistent with the readOnlyHint=true annotation, confirming a read-only operation. However, beyond that, it adds no behavioral details such as what 'detailed information' includes, whether the broadcast must exist, or any side effects. Given the annotations already declare read-only, a score of 3 is appropriate as it meets the minimum but lacks extra context.

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?

The description is a single concise sentence that efficiently communicates the tool's purpose. No unnecessary words or repetition.

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?

The tool has no output schema, and the description does not explain what fields the returned 'detailed information' includes. For an agent to decide if this tool is appropriate, more detail on the response structure would be helpful. However, for a simple get-by-ID tool, it is minimally adequate.

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 coverage is 100% (the one parameter 'id' is described in schema). The description does not add any additional meaning beyond the schema's parameter description. Baseline 3 is correct.

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 clearly states the tool retrieves detailed information about a specific broadcast by ID. It distinguishes from related tools like list_broadcasts (listing) and create_broadcast (creation) through the verb 'Get' and resource 'broadcast by ID'. However, it does not explicitly differentiate from get_broadcast_recipients or other getters.

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?

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives such as list_broadcasts (to get IDs) or get_broadcast_recipients. No prerequisites or context for invocation are given.

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