Leave Swarm cluster

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

Annotations already mark destructiveHint=true and idempotentHint=false. The description adds '[CRITICAL RISK]' and specifies that force is required for managers, which provides additional behavioral context beyond annotations. No contradiction exists.

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 extremely concise: three key pieces of info (risk warning, action, usage hint) in one sentence. Every word is purposeful, with the critical risk flag front-loaded for immediate attention.

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 destructive nature (annotations cover that), the description provides essential guidance. However, it lacks details on immediate consequences (e.g., node removal, service disruption) and return behavior. With no output schema, a brief note on what happens after leaving would improve completeness.

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 description coverage is 100%, with both parameters documented in the schema. The description mentions the force parameter's purpose, but this largely duplicates the schema's description ('Force leave (required for managers)'). Thus, the description adds minimal meaning 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 explicitly states 'Leave the Docker Swarm cluster', clearly identifying the tool's action (leave) and resource (swarm cluster). The title reinforces this, and among sibling tools (e.g., init, join), this is uniquely for leaving, providing clear differentiation.

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 advises 'Use force=true for managers', giving specific guidance on parameter usage. While it doesn't explicitly state when to use this tool vs alternatives, the context of sibling tools makes it clear this is the only leave tool. A more explicit when-not-to-use or prerequisite warning would improve it.

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