bulk_move

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

The description reveals that the operation 'replaces existing mailbox assignments,' implying destructiveness. It also includes the max 50 limit. Without annotations, more behavioral details (e.g., idempotency, partial failure handling) would be beneficial.

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 with two sentences and an Args section. No redundant or extraneous information is present.

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 tool has an output schema but no mention of return values (e.g., success count, failures). For a bulk operation, this is a significant omission. The description leaves out expected results.

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 description coverage is 0%, but the description adds meaning: 'Comma-separated email IDs (max 50)' for email_ids and 'Target mailbox ID' for mailbox_id, which are not present in the raw 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 'Move multiple emails to a mailbox (replaces existing mailbox assignments),' which specifies the verb, resource, and effect. It distinguishes from siblings like 'move_email' (single) and 'bulk_delete' (different action).

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 mentions a max of 50 email IDs in the argument description, providing a constraint. However, it does not explicitly state when to use this tool over siblings (e.g., 'move_email' for single moves) or when not to use it.

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