Delete service

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

The description goes beyond the destructiveHint annotation by detailing exactly what gets deleted (configurations, volumes, connected networks) and the docker cleanup behavior. It also explains how to prevent those deletions by passing flags as false, which is valuable context for safe invocation.

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 two concise sentences. The first sentence states the primary purpose, and the second adds essential default behavior and flag guidance. No unnecessary words or repetition.

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 it is a destructive operation with 5 parameters and no output schema, the description covers the core action, side effects, and flags. It does not mention prerequisites like stopping the service first, but the openWorldHint and default behavior make it sufficiently complete for correct invocation.

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 compensates by explaining the meaning of the boolean flags: 'pass the flags as false to keep them.' It clearly links the options to retaining configurations, volumes, networks, and skipping cleanup, though it does not name each parameter explicitly. The uuid parameter is self-evident.

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 starts with 'Delete a service by UUID,' which is a specific verb and resource, clearly distinguishing it from sibling tools like deleteApplication and deleteDatabase. The noun 'service' is explicit and 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?

The description implies usage for deleting services but does not explicitly state when to prefer this tool over alternatives or when not to use it. It provides no exclusions or alternative tool references, so the guidance is only implied by the tool's purpose.

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