remove_service

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

Annotations already declare destructiveHint=true, so the tool's destructive nature is known. The description adds that it both stops and then removes the service, and returns a boolean. However, it does not disclose any additional behaviors such as irreversibility, failure conditions, or dependency on swarm mode. With annotations present, the description provides minimal extra context.

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 with only three sentences covering purpose, parameter, and return value. It is front-loaded with the core action and wastes no words. Every part earns its place.

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 simplicity (single parameter, boolean return, destructive annotation), the description is largely complete: it states what the tool does, the required parameter format, and the return type. However, it could mention that the service must exist or what happens if the service is already stopped. Still, for a straightforward removal tool, this is adequate.

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 has 0% description coverage (no parameter descriptions). The description fills this gap by explaining that 'service_id - The service id or name,' adding meaning beyond the schema's bare type 'string'. This clarifies what value to provide, which is essential for proper invocation.

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 'Stop and remove a swarm service,' which is a specific verb+resource combination. Among sibling tools like remove_container or remove_volume, it clearly distinguishes by specifying 'swarm service' and mentions the required service_id parameter.

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 stopping and removing a swarm service, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., scale_service, rollback_service) or mention when not to use it. No exclusions or prerequisites are stated.

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