pmg_domain_delete

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

With no annotations, the description fully discloses behavior: mutation, dry-run, execution, dependency on config, side effects on routing rules, irreversibility, and expected return formats for both modes.

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?

Single paragraph but well-structured with key info front-loaded (mutation, dry-run default). Could use bullet points, but each sentence serves a purpose; concise for the information conveyed.

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 the tool's complexity (mutative, irreversible, with dry-run mode and dependencies), the description covers prerequisites, side effects, alternative actions, and return values. Output schema exists, so no need to detail return format further.

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%, baseline 3. Description adds beyond schema: example for domain, explains dry-run vs execute for confirm, and clarifies proximo_target targeting. Provides extra context.

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 states it's a mutation to delete a managed mail domain, with dry-run default. It distinguishes itself from create and list siblings by specifying deletion behavior.

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 explicit guidance: dry-run by default, use confirm=True to execute, needs PROXIMO_PMG_* config, warns about breaking routing rules, notes no undo and recommends recreate via pmg_domain_create.

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