Delete Email Forward

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds substantial behavioral context beyond them: the cascade removal of forwarding MX and SPF records when it is the domain's last forward with no mailboxes, and the consequence that mail to the domain stops being accepted. This is exactly the kind of destructive side-effect disclosure annotations cannot convey.

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?

Two sentences, front-loaded with the operation and identification keys, then the cascade consequence. Dense but every clause carries useful information; no filler.

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?

With no output schema, the description proactively documents the return detail (dnsRecordsRemoved: true) and the full destructive consequence. Combined with 100% schema coverage and clear annotations, an agent has everything needed to invoke it correctly.

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%, so the baseline is 3. The description goes further by explaining why both address and forward_to are required (an address can forward to several mailboxes), adding semantics the schema fields do not state.

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?

States a specific verb+resource ('Delete one email forward') and immediately names the identifying keys, distinguishing it from siblings like list_email_forwards and create_email_forward. An agent can identify the operation and its target without opening any schema.

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?

Points the agent to list_email_forwards as the source of the address/forward_to values, giving clear context for use. It stops short of explicit when-not-to-use guidance or naming an alternative deletion path, but the sourcing instruction is a strong practical cue.

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