bulk_move_emails

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

The only behavioral trait disclosed is 'rate-limited'. With no annotations, the description should cover more (e.g., atomicity, error handling, permission requirements). It fails to do so.

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 only two sentences, which is concise. However, it sacrifices necessary detail for brevity, making it insufficiently informative.

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 four parameters, no annotations, and an output schema that is not referenced, the description lacks completeness. Important details like parameter meanings, source folder role, and response structure are omitted.

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?

The description does not explain any of the four parameters. Schema description coverage is 0%, so both schema and description are silent on what 'account' and 'folder' (source?) mean. This leaves the agent guessing about required inputs.

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 it moves many emails to another folder/label in one call, distinguishing it from the singular 'move_email' sibling. The verb 'move' and resource 'emails' are explicit, though 'folder/label' slightly broadens the scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'move_email' for single moves or 'bulk_delete_emails' for deletion. The mention of 'rate-limited' is a caution but not a usage guideline.

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