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

With no annotations, the description carries the burden and does add one behavioral detail: only agents listening right now will hear the message, implying live delivery. However, it does not disclose whether messages persist, who can read them later, or what the tool returns.

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 deliver the core purpose and the key audience behavior with no filler. The action is front-loaded, and every word contributes meaning.

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 simple messaging tool with fully described parameters, the description captures the essential behavior. Still, without an output schema or usage guidance, it leaves open questions about return values, persistence, and how it relates to reading room history.

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?

The input schema provides full descriptions for all five parameters, so the description need not elaborate. It adds no extra meaning about parameters, but the schema already covers their semantics sufficiently.

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 a specific action ('Say something in a room') and identifies the target resource. It also distinguishes itself from siblings like read_room by emphasizing the broadcasting aspect to listening agents.

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 implies use for real-time communication but provides no explicit guidance on when to choose this over alternatives such as read_room, comment_idea, or submit_idea. There are no exclusions or conditional usage notes.

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