update_swarm

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

The description discloses critical behaviors: token rotation immediately invalidates old tokens but doesn't affect joined nodes, and unlock key rotation requires re-unlocking on restart. This adds context beyond the annotations (readOnlyHint=false, destructiveHint=false).

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 well-structured with a one-sentence purpose, usage guidelines, and an args section. Every sentence adds value, and important information is front-loaded.

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?

All aspects are covered: prerequisites (manager node), behavioral effects, post-rotation steps, and the return type (bool). No gaps remain for the 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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's effect (e.g., 'Issue a new worker join token, invalidating the current one'), adding meaning beyond the boolean type and default.

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 starts with 'Update swarm-wide settings; currently exposes token and unlock-key rotation,' which clearly states the tool's purpose and resources. It distinguishes itself from siblings like 'rotate_swarm_join_token' by offering a combined rotation capability.

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 explicitly requires a swarm manager node and recommends using 'get_swarm_join_tokens' and 'get_swarm_unlock_key' after rotation. It does not explicitly mention alternatives for single-token rotation, but the context is sufficient.

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