archive_email

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

No annotations are provided, so the description carries the burden. It discloses the provider-specific mailbox names ('Archive' for iCloud, 'All Mail' for Gmail), which adds context. However, it does not state whether the operation is reversible, destructive, or requires special permissions, which would be valuable for a mutation tool.

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 concise sentences that front-load the purpose and then add a relevant detail about provider differences. Every word earns its place, with no redundancy or 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?

For a simple move operation with one parameter and no output schema, the description is adequate. It covers the core action and the only special case (mailbox naming). It lacks details on error handling or return behavior, but these are not critical for such a straightforward tool.

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?

The single parameter 'message_ref' is well-documented in the schema with a clear description ('Composite message reference from list_emails or search_emails'). Schema coverage is 100%, so the description adds no additional parameter meaning, but the schema already provides sufficient detail.

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 ('Move an email to the Archive mailbox') and specifies the resource and destination. It also distinguishes from siblings like 'move_email' or 'move_to_junk' by explicitly naming the archive destination.

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 when to use this tool (for archiving) and provides provider-specific context (iCloud vs Gmail mailbox names), but it does not explicitly contrast with alternative moves (e.g., 'move_email' or deletion) or state 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.