move_to_trash

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

Despite annotations already indicating destructiveness, the description adds significant behavioral detail: the action is reversible (not permanent), there is no permanent deletion option on this server, IDs are invalidated after moving, and user confirmation is mandatory. This goes well beyond the annotations and provides essential operational context.

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 compact, front-loaded with the core action, then provides necessary behavioral notes and parameter details. Every sentence serves a purpose, with no redundancy or fluff.

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 one-parameter tool, the description covers the main action, reversibility, server limitations, user confirmation requirement, ID invalidation, and parameter format/limits. The presence of an output schema means return values need not be described. It is complete for safe and correct usage.

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 schema only defines message_ids as a string, but the description explains it expects comma-separated short IDs and enforces a limit of 25 per call. This is critical information for correct invocation and fully compensates for the 0% schema description coverage.

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: moving emails to trash (deleted items), and clarifies it is not permanent deletion. It names the resource (emails) and the target (trash), but does not explicitly distinguish from sibling tools like move_messages or archive_messages, though the specified target makes the purpose unambiguous.

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 provides clear usage context: confirms that permanent deletion is unavailable on this server, instructs to always get user confirmation before execution, and warns that short IDs become invalid after moving, recommending to re-run search_messages for further operations. It does not explicitly name alternative tools, but the guidance on when and how to use is substantial.

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