bulk_delete

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

Beyond the destructiveHint annotation, the description discloses critical behaviors: the XOR relationship between emailIds and match, the irreversible nature of permanent:true versus moving to Trash, the availability of dryRun for preview, and the safety mechanism of maxBatchSize to prevent runaway operations. No contradiction 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 compact and well-structured, leading with the core purpose, then explaining key parameters, and finally providing decision guidance. Every sentence adds value and there is no redundant or filler content.

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 complex tool with 7 parameters, a nested match object, and no output schema, the description covers all essential usage patterns, safety considerations, and sibling alternatives. It gives the agent enough context to invoke the tool correctly and safely.

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?

While the schema covers 86% of parameters, the description adds crucial semantic meaning: the XOR constraint, that folder is required with match, the purpose of dryRun as a preview, and the safety role of maxBatchSize. These details significantly enhance understanding beyond the schema's own descriptions.

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'), the resource ('emails'), and the two modes of operation (explicit ID list or search criteria). It distinguishes itself from siblings by explicitly recommending empty_folder, delete_email, and batch_email_action for alternative scenarios.

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 provides explicit usage context: 'Use when you have specific IDs to delete or want to filter by sender, subject, or date range.' It further provides clear alternatives with 'Prefer' statements, making it obvious when to choose this tool over related ones.

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