Delete Domain

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

The annotations already signal destructive behavior (destructiveHint: true), and the description adds no behavioral detail beyond that, such as whether deletion is permanent, cascades to DNS records, or requires the domain to be unused. There is no contradiction, but the description does not enrich the safety profile.

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 a single, front-loaded sentence with no wasted words. It is concise, though the brevity contributes to the lack of behavioral and parameter detail scored elsewhere.

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 destructive tool with five parameters, three required, and no output schema, a six-word description is insufficient for an agent to confidently call it. It omits parameter semantics, return behavior, and any caveats about the deletion.

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 needed to explain the parameters but only maps 'domain' to domainId and 'app' to appSlug. The required workspaceSlug and optional env/region remain undocumented and unexplained.

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') and resource ('domain from an app'), which clearly identifies the operation and distinguishes it from sibling tools like createDomain, updateDomain, and listAppDomains. It is not a tautology because it adds the app-scoping context.

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 provides no guidance on when to use this tool versus createDomain, updateDomain, or listAppDomains, and no conditions or exclusions. An agent must infer the appropriate context from the name alone.

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