Delete Docker Host

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that deletion is permanent and details the cascading effect on monitors (docker_host cleared, monitors survive). This is meaningful transparency beyond the schema. It misses information about permissions or error handling, but covers the key side effect.

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 sentences long, front-loads the primary action, and adds a critical side-effect clarification without any verbose or redundant wording. Every sentence contributes value.

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 single-parameter delete tool with an output schema, the description is complete: it states the action, permanence, and the consequential effect on related monitors. It does not need to explain return values because an output schema exists, and the low complexity means no other context is required.

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 only parameter is documented in the schema as "The ID of the docker host to delete." The description adds no further semantic detail about the parameter, so the baseline of 3 applies; the schema already provides adequate meaning.

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 specifies a concrete verb and resource: "Permanently deletes a docker daemon connection." It distinguishes this from sibling delete tools like deleteMonitor or deleteNotification by naming the exact target (docker host connection) and by describing the specific side effect on monitors.

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 does not explicitly state when to use this tool versus alternatives, but it communicates an important behavioral consequence: monitors referencing the host will have their docker_host cleared, while the monitors themselves are not deleted. This implicitly warns users not to expect monitor deletion, providing some usage context.

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