deleteEmailForward

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Delete', which implies mutation, but it does not explain whether deletion is permanent, what effects it has, or whether any authorization is required. This is a minimal disclosure, not a transparent one.

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 with the action front-loaded. It contains no redundant filler, though the generic API reference link adds limited specific value. It is appropriately sized but not especially rich.

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?

This is a mutation tool with no annotations and no output schema, yet the description only states the operation. It lacks information about return values, error behavior, prerequisites, or how this relates to the existing email-forward lifecycle. An agent can infer the basic action but not confidently handle edge cases or verify success.

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?

The input schema already describes both parameters: 'domain' and 'email' with the email field noted as 'Local part only, e.g. info'. Schema description coverage is 100%, so the description adds no additional parameter meaning. A baseline of 3 is appropriate because the schema handles the parameter semantics.

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 operation as 'Delete an email forward', using a specific verb and resource. It distinguishes itself from sibling tools like configureEmailForward and listEmailForwards by naming the delete action explicitly.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites, and no exclusions. Sibling tools like listEmailForwards and configureEmailForward exist, but the description does not help an agent decide which one fits the scenario.

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