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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), which lowers the bar, but the description adds nothing beyond the operation name — no note that the message is removed from its source folder, whether the move is reversible, or how folder names are resolved.

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?

One short, front-loaded sentence with no wasted words, but the brevity reflects under-specification rather than disciplined concision. It fits the 'minimum viable' band.

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?

An output schema exists, so return values need no explanation, but for a mutation tool with 0% schema description coverage the description leaves the agent without source-folder semantics, destination validation behavior, or error conditions. Incomplete for the operation's complexity.

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 must compensate and it does not: it only repeats the parameter name 'dest_folder' and says nothing about 'uid' (message identifier format) or 'folder' (the source folder, defaulting to INBOX). With three undocumented parameters, this is a significant gap.

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?

States a specific verb and resource ('Move a message'), which an agent can distinguish from sibling operations like flag_message or read_message. It stops short of any explicit sibling differentiation, so it lands at a clear-but-generic 4.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisite conditions (does the destination folder need to exist?), and no mention of what happens to the source copy. The description is purely a restatement of the operation.

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