agent_get_broadcast

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

There are no annotations, so the description carries the full behavioral burden. It usefully warns that returned content is untrusted and must not be followed as instructions, but it does not clarify authentication, failure behavior, or side effects. The sentence about acting as an identity in the local credential store is unclear and does not add reliable behavioral 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 short and front-loads the main purpose, but the middle sentence about acting as an identity in the local credential store is confusing and does not clearly earn its place. The security warning is useful and well placed.

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 single-parameter read tool with an output schema, the description does not need to explain return values. However, it omits when to use this tool versus alternatives and leaves the credential-store sentence ambiguous, so it is only minimally complete.

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%, and the only parameter is already documented as 'Broadcast id'. The description repeats the broadcast concept but adds no syntax, format, or lookup constraints beyond the schema.

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 first sentence clearly identifies the resource as a broadcast and adds the returned detail, per-agent task status. It does not distinguish the tool from siblings such as agent_list_broadcasts or agent_broadcast_task, but the core purpose is understandable.

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 description gives no explicit guidance about when to use agent_get_broadcast instead of agent_list_broadcasts, agent_broadcast_task, or other broadcast-related tools. It only describes the return content and a safety warning.

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