swarm_update

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

The description states token rotation invalidates the old token immediately, which is destructive, but annotations have destructiveHint=false, creating a direct contradiction. This misleads the agent about the tool's impact.

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 brief intro, important usage notes in prose, and an args list. It is front-loaded and each sentence adds value, though the args list could be slightly more concise.

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's complexity (3 boolean params, significant side effects), the description covers prerequisites, operational behavior, consequences, return type, and post-rotation actions, making it fully comprehensive.

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 0%, but the description fully explains each boolean parameter's effect (e.g., 'Issue a new worker join token, invalidating the current one'), adding clear semantics beyond the 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 it updates swarm-wide settings for join-token and unlock-key rotation, using a specific verb ('Update') and resource, and distinguishes from sibling retrieval tools by noting they are used after rotation.

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 specifies prerequisite ('Must be called on a swarm manager node'), explains when to use (token/unlock key rotation), and describes consequences (immediate invalidation, re-unlock requirement), with references to sibling tools for post-rotation retrieval.

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