Move Email to Spam

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

Annotations already indicate destructiveHint=true. The description adds context that a confirmed=true parameter is required, which is a behavioral detail beyond annotations. No contradictions, but it doesn't fully elaborate on consequences (e.g., spam filtering effects).

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 concise sentences: first states purpose, second adds behavioral caveat. No unnecessary words, and the description is front-loaded with the main action.

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 simplicity and the presence of an output schema (handling return values), the description is mostly complete. It could mention edge cases like moving an already-spam email being a no-op, but overall sufficient.

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 67%, and the description adds minimal parameter semantics beyond what the schema provides. It mentions the confirmed parameter's role but does not describe emailId or sourceFolder in detail. Adequate but not compensative for low coverage.

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 the verb 'Move' and the resource 'email to the Spam folder'. It also distinguishes from siblings by noting it's a convenience wrapper for move_email with Spam as target.

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 some usage guidance by noting the destructive nature and confirmation requirement. However, it does not explicitly state when to use this tool over alternatives like move_email or move_to_trash, nor does it mention exclusions.

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