rlm_swarm_events

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

With no annotations, the description should disclose behavioral traits such as read-only nature, ordering, pagination, or required permissions. The description only says 'query and filter,' omitting that it returns limited results (default 50) and likely only recent events. No mention of safety or side effects.

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 a single short sentence, but it is under-specified. It sacrifices essential details for brevity, making it less useful. A concise description should include key behavioral aspects.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It doesn't explain what constitutes an 'event,' the return format, ordering, or how filtering works. The schema helps but leaves many gaps for an AI agent.

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 80%, so most parameters have descriptions. The tool description adds no additional meaning beyond the schema. It does not explain the purpose of event_type or agent_id or how filtering interacts with them.

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 'Query and filter broadcast events in a swarm,' specifying the action (query/filter) and resource (broadcast events). It distinguishes from sibling tools like rlm_swarm_members (list members) and rlm_broadcast (send events), though it could be more precise about the type of events.

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 provides no guidance on when to use this tool versus alternatives like rlm_broadcast (sending events) or rlm_context_query (querying context). There is no mention of prerequisites or typical usage scenarios.

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