move_email

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

With no annotations and only a one-word description, no behavioral traits are disclosed. It does not indicate whether moving is destructive, permissions needed, or side effects. This is a critical gap 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?

The description is a single, direct sentence with no redundancy or unnecessary words. It is appropriately concise.

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 tool's low complexity but missing required inputs, the description is entirely insufficient. It does not explain how to specify the email or destination mailbox, leaving the tool unusable as defined.

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?

Although there are zero parameters (baseline 4), the description fails to explain how the tool determines which email to move and to which mailbox. The empty schema combined with no parameter information leaves the tool ambiguous.

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 'Move email to a different mailbox' clearly indicates the action and target resource. However, it does not differentiate from other email or move tools; while no direct sibling does this, the description could be more specific about scope.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context. Without this, an agent may misuse the tool.

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