archive_emails

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

Describes the key behavioral trait of auto-detecting the Archive folder via RFC 6154 flag with fallback, which is crucial for an archive operation. Could mention reversibility or flags affected, but given no annotations, this is substantial.

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 sentences, front-loaded with the action, no unnecessary words. Every element serves a purpose.

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 moderate complexity (auto-detection of archive folder) and existence of output schema, the description covers essential aspects: the prerequisite (list_emails_metadata) and the folder detection mechanism.

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. Description adds value by clarifying that email_ids come from list_emails_metadata and explaining the mailbox default, exceeding baseline.

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 specifies the action 'archive' and the resource 'emails', distinguishing it from siblings like delete_emails and move_emails by explaining the auto-detection of the Archive folder.

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?

Explicitly instructs to use list_emails_metadata first to obtain email_ids. Does not explicitly state when not to use, but context from siblings like delete_emails and move_emails helps differentiate.

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