broadcast_message

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

No annotations are present, so the description must carry the full burden of explaining side effects and behavioral implications. It only states 'Broadcast a message to all agents' without disclosing whether messages are persisted, notifications triggered, or permission requirements.

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 only two sentences, but the second sentence is a near-verbatim paraphrase of the first ('Broadcast a message to all agents' vs 'Send a message to all agents working on the project'). It adds no new information and should be removed for true conciseness.

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 relatively simple messaging tool with fully documented schema, the description is adequate but thin. It lacks usage differentiation, behavioral caveats, and any context about message_type variations, making it minimally complete rather than thorough.

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%, so all parameters have basic descriptions in the schema. The tool description adds no additional parameter-level semantics, but the schema alone is adequate for understanding the inputs.

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 uses a specific verb 'Broadcast' and clearly identifies the resource: 'a message to all agents in a project.' This distinguishes it from sibling tools like send_message, which implies a single recipient. The second sentence is redundant but does not harm clarity.

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 guidance is provided on when to use this tool versus alternatives such as send_message. There are no exclusions, prerequisites, or examples of appropriate scenarios. The description merely states what it does, not when to choose it.

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