Archive email

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

Describes the action (move to archive) and special-use awareness, but lacks details on side effects, permissions, or error conditions. Annotations indicate non-read-only and non-destructive, consistent with the description.

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?

Single sentence, no superfluous words. Effective front-loading of the core 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?

For a simple archive action, the description covers the basic operation but lacks usage guidelines and parameter details. Could be more helpful given the presence of sibling tools like email_move.

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?

Only the server parameter has a schema description. The description does not explain the uid or folder parameters, leaving their semantics unclear despite low schema coverage (33%).

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 archives an email by moving it to the archive folder, with special-use awareness. This verb+resource pair distinguishes it from siblings like email_move.

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?

No guidance on when to use this tool versus alternatives like email_move. The description does not mention when not to use it or provide context for selecting this tool.

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