bulk_delete

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

Without annotations, the description fully discloses behavior: moves to Trash if permanent=False and Trash folder exists, else permanently deletes. It explains edge cases like localized folder discovery and always-permanent deletion from Trash.

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 concise, using clear bullet-like structure. Every sentence is informative, starting with the main purpose and then detailing behavior variations in an organized manner.

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?

Given three parameters and no output schema, the description covers behavior, edge cases (Trash, permanent flag), and folder discovery. It could mention return values but remains adequate for an agent to invoke correctly.

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?

With 0% schema coverage, the description adds meaning for 'permanent' (default False, effect) and implies 'email_ids' are the messages to delete. However, it does not explicitly describe the 'folder' parameter beyond being the container.

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 messages at once, with specific behavior for permanent vs soft delete. It distinguishes itself from sibling tools like 'delete_email' and 'empty_trash' by focusing on bulk deletion.

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?

It explains when to use permanent=True vs False, and the special case of deleting from Trash. It implies appropriate use cases, but does not explicitly state alternatives like 'bulk_move' or 'bulk_set_flags'.

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