remote_swarm_remove_target

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

No annotations are provided, so the description carries full transparency burden. It does disclose a significant side-effect—closing the target's session—which goes beyond the schema. However, it does not mention reversibility, impact on running processes, or any permissions required, leaving some gaps for a destructive operation.

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 a single short sentence that directly states the operation and adds a meaningful side-effect in a parenthetical. Every word earns its place; there is no redundancy or unnecessary detail.

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 destructive operation, the description covers the purpose and a key behavioral consequence. However, it doesn't elaborate on what happens to the session or whether the action is reversible, which might be useful given there is no output schema. Still, it is adequate for 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 provides complete descriptions for both parameters (swarmId and targetId), so the description adds no extra parameter semantics. With 100% schema coverage, a baseline of 3 is appropriate; the description does not need to compensate.

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 the action 'Remove' and the resource 'a target from a swarm', which is specific and distinguishes it from related sibling tools like remote_swarm_add_target and remote_swarm_end. The parenthetical 'closes its session' adds valuable scoping and clarifies the operation's exact effect.

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 verb and object make the intended use obvious: use when you need to remove a target from a swarm. It doesn't explicitly mention when not to use it or contrast with alternatives, but the context is sufficiently clear given the sibling tool names and the explicit parenthetical.

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