gmail_prepare_bulk_label_query

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

No annotations exist, so the description carries full burden. It discloses that the operation is a preview/stage and that nothing changes until confirmation, indicating nondestructive behavior. However, it does not mention authentication, rate limits, or edge cases.

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?

Two brief sentences, front-loaded with purpose. No redundant information.

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?

No output schema is provided, and the description lacks any mention of return values (e.g., count of matched messages). Additionally, two parameters (max_messages, create_missing_label) lack schema descriptions and are not elaborated in the description. For a preview tool, more detail on output is expected.

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 67%, with 4 of 6 parameters having descriptions. The description adds the context of 'capped', but does not explain parameters like create_missing_label or max_messages beyond what the schema provides. Baseline is 3 due to moderate coverage.

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 (preview and stage), resource (capped query-based bulk label operation), and distinguishes from siblings like gmail_apply_labels_to_messages which applies immediately. It also emphasizes that nothing changes until confirmation.

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 clear context: use this to prepare a bulk label operation, then confirm with gmail_confirm_bulk_label_operation. It implies when not to use (e.g., for immediate application), but does not explicitly list alternatives or exclusions.

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