gmail_delete_filter

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

The description only says 'Delete', implying a destructive operation, but provides no additional behavioral context such as whether the action is reversible, any required permissions, or side effects. Without annotations, this is insufficient for an agent to understand fully what happens.

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?

A single, front-loaded sentence with no unnecessary words. It efficiently conveys the core action and required identifier.

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?

For a delete operation with no annotations or output schema, the description should provide context on obtaining the filter ID (e.g., from gmail_list_filters) and the effect of deletion. It lacks completeness for an agent to use safely without prior knowledge.

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 baseline is 3. The description adds minimal value beyond the schema—it restates that deletion is by filter ID but does not elaborate on the 'account' parameter. The schema already describes both parameters adequately.

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 ('Delete'), the resource ('one Gmail filter'), and the key identifier ('by its filter ID'). It is specific and distinguishes from sibling tools like gmail_create_filter or gmail_list_filters.

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?

No guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., needing to call gmail_list_filters first), and no warning about irreversible nature of deletion. The description assumes the user knows to use this only when they have a valid filter ID.

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