email_forward_remove

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'removes' a rule, but does not mention whether the action is permanent, what happens if the rule does not exist, or any prerequisites. For a destructive operation, more transparency about side effects is needed.

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 sentence that front-loads the action ('Remove') and concisely states the resource and parameter. No wasted words or unnecessary detail.

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?

The tool is simple, with one parameter and no output schema, and the description captures the core function. However, it lacks context about the destructive nature, error behavior, or how this relates to adding/listing forwarding rules, leaving some gaps for an agent.

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% for the single parameter, and the description merely restates the parameter's purpose ('for the given source email address') without adding extra meaning. Baseline score of 3 is appropriate since the schema already fully documents the parameter.

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 ('Remove') and identifies the resource ('email forwarding rule') and the key parameter (source email address). It clearly distinguishes this from sibling tools like email_forward_add, email_forward_update, and email_forward_list, which involve different actions.

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 usage is implied by the verb 'Remove' – the user would use this when they want to delete a forwarding rule. However, there is no explicit guidance on when not to use it or mention of alternatives, such as email_forward_list for checking existing rules.

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