bulk_delete

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

The description goes beyond the destructiveHint annotation by detailing the irreversibility of permanent deletion, the preview capability with dryRun, and the additional confirmation required when permanent:true and destructive action confirmation is enabled. No contradictions with annotations.

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 three sentences with no extraneous words. It front-loads the primary action ('Delete multiple emails') and then concisely explains key parameters and constraints. Every sentence adds necessary information.

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 description covers the key behavioral aspects and parameter interactions. However, it does not mention the return value or how to interpret success (e.g., count of deleted emails). Given no output schema, a brief note on the response would improve completeness. Still, the destructive nature is well-addressed.

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?

Given 86% schema coverage, description adds significant value: it explains the XOR relationship between emailIds and match, clarifies that permanent=false moves to Trash rather than just 'not permanent', and highlights the confirmation requirement. These nuances are not evident from the schema alone.

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 tool deletes multiple emails in one pass, distinguishes between two input modes (emailIds or match criteria with XOR), and explains the effect of the permanent flag. It differentiates from sibling tools like delete_email (single) and trash_email (single) by emphasizing batch operation.

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 explains the XOR requirement for input methods and the purpose of dryRun and permanent flags. However, it does not explicitly state when to prefer this tool over alternatives like trash_email or delete_email, nor does it provide when-not-to-use guidance. The context is clear but lacks explicit exclusions or alternative recommendations.

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