swarm_update

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

Annotations indicate mutation and non-destructive. The description adds critical behavioral details: token rotation invalidates old tokens immediately, existing joined nodes unaffected, unlock key rotation requires re-unlock on restart. Also documents return type bool.

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?

Well-structured: purpose, prerequisites, behavioral details, parameter list, return type. Each sentence adds value without verbosity. Front-loaded with main action.

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?

Covers purpose, prerequisites, side effects, parameter meanings, return type, and relevant sibling tools. No output schema needed beyond bool. Complete for a mutation tool with three boolean flags.

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?

Despite 0% schema coverage, the description includes an 'args' section that fully explains each boolean parameter: rotate_worker_token, rotate_manager_token, rotate_manager_unlock_key. This compensates for the lack of parameter descriptions in the input schema.

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 the tool's purpose: updating swarm-wide settings, specifically for join-token and unlock-key rotation. It distinguishes itself from sibling tools like swarm_join_tokens and swarm_unlock_key by focusing on rotation rather than retrieval.

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?

Explicitly states prerequisite 'Must be called on a swarm manager node.' Provides context on when to use (for rotation) and references sibling tools for retrieving new tokens after rotation. It also explains consequences like token invalidation.

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