rlm_swarm_update

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

No annotations are provided, so the description carries full burden. It discloses that it performs an update (mutation) and requires admin access, with constraints on timeouts. It does not detail reversibility or effects on omitted optional fields.

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 concise with a header and bullet points, no unnecessary words, and clearly front-loaded with the action and access requirement.

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 6 parameters (1 required) and no output schema or annotations, the description covers all parameters, admin requirement, and constraints. It lacks details on immediate effects or error handling but is otherwise adequate.

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 100%, but description adds value beyond schema by noting 'max_agents: plan-limited' and providing context like 'What the swarm is for' for description, plus repeating range constraints in a readable format.

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 'Update swarm configuration' and lists specific updatable settings, distinguishing it from sibling tools like rlm_swarm_create and rlm_swarm_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?

It mentions 'requires ADMIN access' and lists updatable fields, providing context for when to use. However, it does not explicitly state when not to use or compare to alternatives like rlm_swarm_create for creation.

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