Archive Email

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

The description adds value beyond annotations by noting that labels are lost when the email is moved and that it is a convenience wrapper. Annotations provide no destructive or idempotent hints, so the description fills a gap.

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, no wasted words, and front-loaded with the core action. Every sentence adds value.

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 extensive list of sibling tools and the presence of an output schema, the description is complete enough. It covers the key behavioral note (label loss) and the wrapper nature, ensuring the agent understands when and how to use it.

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 50%, with emailId lacking a description. The tool description does not explain emailId or add parameter meaning beyond the schema's sourceFolder description. Compensating for the missing emailId description would have improved clarity.

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 moves an email to the Archive folder and positions it as a convenience wrapper for move_email targeting Archive, distinguishing it from siblings like move_email and 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 implies usage for archiving but does not explicitly state when to use this tool versus alternatives like move_email with a different target folder. The warning about label loss provides context but no direct guidance on when not to use the tool.

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