email_archive

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

Discloses key effect (removes from inbox, not deletion) but lacks details on reversibility, label behavior, or auth requirements. No annotations provided, so description carries burden.

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?

One sentence, efficiently communicates action and key distinction. No filler.

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?

Simple action with one parameter. No output schema needed. Describes essential behavior. Could mention result (e.g., success) but not required.

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 100% for the only parameter. Description adds no extra meaning beyond the schema's description of 'message_ids'.

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?

Clearly states the tool archives messages, removes from inbox, and specifies it does not delete. Differentiates from sibling tools like email_trash and email_delete.

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?

Implies usage context (archiving vs deleting) but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives like email_trash or email_add_label.

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