pmg_domain_delete

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

Discloses mutation, dry-run behavior, need for explicit confirm, and potential side effects on mail routing. Mentions PMG version and API path. No annotations provided, so description carries full burden.

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?

Three concise sentences: purpose, execution details, and warnings. No wasted words, well-structured.

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?

Adequate for a delete tool: covers purpose, parameters, side effects. Output schema exists so return values need not be described. Could mention output briefly.

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 33% (only proximo_target described). Description adds meaning for 'domain' and 'confirm' parameters but does not detail all. Compensates partially for low coverage.

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?

Description clearly states 'delete a managed mail domain' with verb and resource. Distinguishes from sibling tools like pmg_domain_create and pmg_domains_list.

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?

Provides guidance on dry-run default and confirm=True for execution. Warns about routing rule breakage and mentions required config. No explicit comparison to alternatives, but no alternative delete exists.

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