service_remove

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

The description discloses the destructive nature in detail: 'Deletes the service definition and shuts down its tasks — no confirmation, no undo.' This adds significant context beyond the destructiveHint annotation, and it also notes the swarm manager requirement.

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 compact and well-structured: action, requirements, behavior, alternative, and return value are all covered in a few sentences without 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?

For a simple tool with one parameter and an output schema, the description covers purpose, prerequisites, behavior, alternatives, and the return value. No critical gaps are present.

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?

With 0% schema description coverage, the description is the sole source for the parameter. It states 'id_or_name - The service id or name', which merely restates the parameter name and adds little depth. It does not clarify format, validation, or existence requirements.

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 uses a specific verb ('Stop and remove') with a clear resource ('swarm service'). It explicitly distinguishes itself from the sibling tool by noting that service_scale keeps the definition, making the purpose unambiguous.

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?

It states a prerequisite ('Requires a swarm manager') and explicitly provides an alternative: 'To stop work but keep the definition, service_scale to 0 replicas.' This gives clear when-to-use and when-not-to-use guidance.

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