move_email

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

Annotations are absent, so the description must cover behavioral traits. It states the action (move) and that it returns a confirmation, but it does not disclose side effects (e.g., if flags change, if the move is reversible) or details about the move operation. This is minimally adequate for a simple 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 extremely concise: one sentence for purpose followed by a structured list of arguments. No unnecessary words or redundancy. Every line is functional.

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 3 required params, no output schema, and no annotations, the description covers the basic action and return value but lacks context about error handling, whether the move is permanent, or how it differs from a copy. The sibling 'bulk_move' suggests a need to specify this moves a single email, but that is not explicit.

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 0%, so the description compensates by explaining each parameter: folder as source, email_id, and destination as destination folder name. This adds meaning beyond raw property names and types, though it lacks format constraints or examples.

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 'Move an email to another folder.' This specifies the verb 'move' and the resource 'email' to a destination folder, distinguishing it from siblings like bulk_move (multiple) and forward_email (copy to recipient).

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 is given on when to use this tool vs alternatives. With siblings like bulk_move, an agent would benefit from knowing this moves a single email, but the description does not provide any usage context, prerequisites, or exclusions.

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