gmail_batch_delete

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

With no annotations provided, the description effectively discloses the irreversible nature ('cannot be undone') and that it operates on multiple messages. However, it lacks details on side effects (e.g., label removal), required permissions, or rate limits.

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, front-loaded sentence that conveys the essential information (permanent batch delete) with zero 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?

For a tool with one parameter and no output schema, the description covers the core behavior adequately. However, it could be more complete by explicitly comparing to gmail_delete or gmail_trash, and by mentioning impact on threads or labels.

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 the parameter description in the schema ('Comma-separated message IDs to delete') already conveys the format. The tool description adds no additional semantic context beyond what the schema provides, earning a baseline 3.

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 verb 'delete', resource 'multiple Gmail messages', and key characteristics 'at once' and 'permanently (cannot be undone)'. It distinguishes from sibling tools like gmail_delete (single message) and gmail_trash (soft delete) by emphasizing the batch and irreversible nature.

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 use for batch permanent deletion but does not explicitly state when to use vs alternatives like gmail_delete for single messages or gmail_trash for reversible deletion. No 'when not to use' guidance is provided.

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