Remove Mailbox Forwarding

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds 'Remove' which aligns, but does not disclose additional behavioral traits such as whether the operation is reversible or what happens to associated data. With annotations covering the safety profile, the description provides marginal extra value.

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 concise sentence that efficiently communicates the tool's purpose. It is appropriately sized and front-loaded, with no wasted words.

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 presence of an output schema (indicated), annotations, and 100% schema coverage, the description is mostly complete for a simple delete operation. It lacks explicit usage guidelines but the overall context is sufficient.

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% and both parameters ('id' and 'forwarding_id') are described as 'ShipMail resource ID.' with regex patterns. The description adds no further meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 the action ('Remove') and the resource ('a pending or active mailbox forwarding destination'). The verb and resource are specific, and the tool is distinct from siblings like 'create_mailbox_forwarding' and 'list_mailbox_forwarding'.

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 implies usage for removal of forwarding destinations, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions. The context from the tool name and sibling tools makes the use case clear, but explicit guidance is lacking.

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