test_bulk_operations

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

No annotations provided. The description says 'safe operations' but does not clarify that when dryRun is false, actions actually modify emails. This omission is critical for a test tool.

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, efficient sentence that conveys the core purpose. No 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?

With no output schema and no annotations, the description is too brief. It lacks details about what 'test' means, success/error behavior, or how it differs from sibling bulk tools.

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 descriptions for dryRun and limit are present. The tool description adds context about finding recent emails and safe operations, but does not add new meaning beyond the schema.

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 is for testing bulk operations by finding recent emails and performing safe operations like mark read/unread. It distinguishes from actual bulk tools by the 'test' intent, though it doesn't explicitly name a sibling.

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?

Implies use for testing before actual bulk operations, but does not explicitly state when to use this vs sibling tools like bulk_mark_read or bulk_add_labels. No when-not or alternatives mentioned.

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