remote_swarm_end

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral side effect that ending a swarm closes all its sessions, and the 'all' special case. However, it does not mention reversibility, required permissions, or effects on underlying processes, leaving gaps in behavioral transparency.

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?

Two short sentences, front-loaded with the action, and no wasted words. The description is appropriately sized for a simple end operation.

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 tool with one parameter, no output schema, and no annotations, the description adequately covers the main action, side effect, and special value. It lacks details on error handling or return values, but these are less critical for a straightforward terminating operation.

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 100% and the schema description already explains the 'all' value. The description redundantly repeats 'Use swarmId='all'' without adding extra semantic details beyond what the schema provides, so it adds no significant value.

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?

Clear verb 'End' + resource 'swarm', specifies it closes all its sessions, and includes the special value 'all'. This distinguishes it from sibling tools like remote_session_end (which ends a single session) and remote_swarm_interrupt (which sends an interrupt).

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 implies usage for ending a swarm, with the special instruction to use swarmId='all' for ending all swarms. However, it does not explicitly mention when not to use this tool or how it compares to alternatives like remote_session_end for individual sessions.

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