agent_list_broadcasts

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

With no annotations, the description carries the full burden, and it does add one genuinely valuable behavioral fact: returned content is untrusted third-party data and must not be treated as instructions. It omits other traits an agent would want — pagination, ordering, scope of 'your' broadcasts, or any auth requirement.

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?

Four short sentences, front-loaded with the action, and no padding. The credential-store sentence is terse to the point of ambiguity but still brief rather than verbose.

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?

An output schema exists, so return-value explanation is not required, and the untrusted-data warning covers the main safety concern. What is missing is any differentiation from agent_get_broadcast, which is the most likely source of a wrong tool selection.

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% for the single optional 'status' parameter (active or completed), so the schema already carries the semantics. The description adds nothing about filtering by status, 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 ('List your broadcasts'), which is clear on its own. However, it does not distinguish itself from the closely named sibling agent_get_broadcast, leaving the agent to infer that this returns a collection while that one returns a single item.

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 guidance on when to call this versus agent_get_broadcast or agent_broadcast_task. The clause 'Acts as the identity in the local credential store' gestures at context but does not tell the agent when this tool is the right choice.

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