Remove Label from Email

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

Annotations indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds value by specifying the non-destructive nature (email remains in original folder) and the UID space nuance. This provides behavioral context beyond annotations. Could mention error handling or reversibility, but sufficient.

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 two sentences, each carrying important information. It is front-loaded with the core action and immediately addresses the critical nuance. No unnecessary 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?

Given the presence of an output schema and annotations, the description effectively covers the core operation, the non-destructive effect, and a key caveat about UID space. It does not explain error conditions or what happens if the label doesn't exist, but overall it provides sufficient context for an AI agent to use the tool 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?

Schema coverage is 100%, so baseline is 3. The description adds crucial meaning for the 'emailId' parameter by clarifying it must be the UID in Labels/{label} and not the inbox UID. This goes beyond the schema description. No extra context for 'label' or 'account_id' beyond schema, but the addition elevates the score.

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 action 'Remove a label from an email' and explains that the email remains in its original folder, distinguishing it from deletion or moving. This is specific and differentiates from sibling tools like 'delete_email' or 'move_to_trash'.

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 gives explicit guidance on the UID requirement: the UID must be from the Labels/{label} folder, not the INBOX. This tells the agent when to use this tool (only if you have the label-folder UID) and implies that if you have the inbox UID, you need to get the label UID first. However, it does not mention alternatives like 'bulk_remove_label' 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.