rlm_broadcast

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

No annotations provided. The description only states basic action without revealing behavioral traits like side effects, return behavior, permissions, or whether the event is synchronous. With no annotations, the description fails to compensate.

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?

Single sentence is concise and front-loaded. However, it could include a bit more detail without becoming 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?

No output schema, no annotations, and description is too brief for a tool with 4 parameters including a nested object. It omits important usage context like return value, error conditions, and event format.

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 50% (event_type and payload have descriptions, but swarm_id and agent_id do not). The tool description does not add any meaning beyond the schema, leaving parameter semantics incomplete.

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?

Description clearly states the action (send event) and scope (to all agents in the swarm). It distinguishes from sibling tools like rlm_swarm_events or rlm_swarm_members by specifying broadcasting to all 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?

No guidance on when to use this tool vs alternatives, no prerequisites or exclusions mentioned. The description is purely functional without context for decision-making.

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