Move Email to Spam

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

Annotations already flag destructiveHint: true, but the description adds that it requires 'confirmed: true' to execute, which is a key behavioral constraint not captured by the annotation flags alone.

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?

Two sentences, front-loaded with purpose and a clear behavioral note. Every word earns its place; no redundancy.

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 simple nature of the tool, the description is mostly complete. Output schema exists but the description does not explain return values; however, the schema covers that. Could mention the effect on the email or any side effects, but it's sufficient for a straightforward action.

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?

With schema description coverage at 75%, the description does not add meaning beyond what the input schema already provides. It mentions the 'confirmed' requirement but that is also documented in the schema. No additional parameter insight is given.

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 the Spam folder' and identifies it as a convenience wrapper for move_email targeting Spam. This specific verb+resource combination distinguishes it from siblings like move_email or move_to_folder.

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 notes it is a convenience wrapper and that it is destructive requiring confirmation. It implies use when you want to move to Spam specifically, but does not explicitly contrast with alternatives or discuss when not to use it.

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