rotate_swarm_join_token

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

The description clearly discloses the behavioral effect: invalidating old tokens immediately, while unaffected nodes, pending invitations fail. It also explains the implementation (wraps swarm.update and re-reads tokens). Annotations only provide readOnlyHint and destructiveHint, so the description adds significant value beyond them.

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 two paragraphs, front-loaded with the main purpose and effects. Every sentence adds value: action, consequences, parameter list, return value. No redundant or filler content.

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?

For a simple two-parameter tool with no output schema, the description covers purpose, effect, return value, and parameter constraints. It lacks mention of prerequisites (e.g., swarm must be initialized) or error conditions, but these are minor given the tool's simplicity.

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?

The input schema has zero description coverage, but the description lists both parameters with clear semantics: 'Rotate the worker join token' and 'Rotate the manager join token'. It also adds the constraint that at least one must be True, which is not present in 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 states exactly what the tool does: rotate worker and/or manager join tokens. It uses specific verb 'Rotate' and resource 'worker and/or manager join token', and distinguishes from sibling tools like get_swarm_join_tokens by clarifying it invalidates old tokens and returns new ones.

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 notes that at least one parameter must be True, which is helpful, but it does not explicitly compare to alternatives like get_swarm_join_tokens or update_swarm. There is no 'when to use' or 'when not to use' guidance, leaving the agent to infer usage context from the sibling list.

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