move_message

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

The description reveals a critical behavioral trait: 'Moving a message adds the destination label but may not remove the original,' which is essential for an AI agent to understand the side effects. Since no annotations are provided, the description carries the full burden, and it does so well for this key aspect.

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 very concise with two sentences. The first sentence states the action, and the second adds important context about label behavior. No unnecessary words or repetition.

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 no annotations, no output schema, and 4 required parameters, the description covers the core action and a key behavioral nuance. However, it lacks information about return values, error conditions, or required permissions, which would help the agent handle failures gracefully.

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?

All 4 parameters are fully described in the input schema (100% coverage), so the description does not need to add much. The parameter names are self-explanatory, and the description does not elaborate beyond what the schema provides, which is acceptable.

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 a message to a different mailbox' with a specific verb and resource. It also explains Gmail's label behavior, which distinguishes it from a simple folder move. However, it does not explicitly mention that this tool operates on a single message, which could be inferred from the name but not clarified.

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 versus alternatives like 'move_messages' (plural). The description does not specify prerequisites, such as existing mailboxes or required permissions. Usage context is only implied by the tool name.

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