swarm_leave

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

Beyond the destructiveHint annotation, the description discloses that service tasks are rescheduled, managers refuse without force, and the node remains listed as 'down' until node_remove is run. These details give an agent an accurate picture of the operation's consequences and lifecycle.

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 front-loaded with the core purpose in the first sentence, followed by concise behavioral details and an args/returns summary. Every sentence contributes essential information with no redundancy.

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?

With one parameter and an output schema, the description covers the operation's effect, parameter semantics, return type, and a follow-up action (node_remove). It is complete for an agent to invoke and reason about the tool.

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 schema has zero description coverage, but the description fully explains the 'force' parameter as 'Force leave even if the node is a manager' and clarifies that manager nodes refuse without it. This meaningfully compensates for the schema's lack of parameter documentation.

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 'Leave the current swarm' with a specific verb and resource, clearly distinguishing it from siblings like swarm_join and swarm_init. It further clarifies scope by explaining service task rescheduling and the lingering down state, which differentiates it from node_remove.

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 explains when force=True is required (for managers to avoid breaking raft quorum) and mentions the follow-up node_remove, providing strong usage context. It does not explicitly name alternative tools, but the guidance is clear enough for an agent to decide when to use this tool.

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