delete web domain

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

Annotations already declare destructiveHint=true, so the description only needs to add context beyond that. It usefully discloses that files are deleted along with the domain and mentions the exact command executed. There is no contradiction with the annotations.

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 short sentences with the core action front-loaded. The second sentence about the verified command is somewhat tangential but not enough to significantly reduce clarity.

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?

The destructive nature and target are clear, and the output schema covers return values. However, the description omits guidance about the 'restart' parameter, side effects, and when to prefer sibling tools, leaving meaningful gaps for a destructive operation.

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 description coverage is only 25%, so the description carries a heavier burden for explaining parameters. It provides no insight into the 'restart' parameter and does not clarify how 'user' or 'domain' relate to the deletion beyond what their names imply.

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 ('Delete') with a clear resource ('a web domain') and adds scope ('and its files'), making the tool's purpose unmistakable. It is easily distinguished from sibling delete_* tools by the 'web domain' resource.

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?

There is no guidance about when to use this tool versus alternatives, such as suspend_user or delete_dns_domain. The description does not state prerequisites, confirmations, or consequences beyond the initial deletion, leaving the agent to infer appropriate usage.

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