Move Email to Custom Folder

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

Annotations already indicate non-readOnly, non-destructive, non-idempotent. The description adds behavioral context beyond annotations through the sourceFolder parameter description, which warns about silent no-op if source is wrong or if moving to same folder.

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 main description is concise (one sentence). However, the sourceFolder parameter description is lengthy but justifiably detailed. The overall structure is front-loaded and effective.

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 existence of an output schema, the description need not explain return values. The sourceFolder parameter description adds critical context for correct usage. However, the emailId parameter lacks any description, which is a completeness issue.

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% (folder and sourceFolder have descriptions, emailId does not). The tool description itself adds no parameter information beyond what the schema provides. The missing emailId description is a notable 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?

Description clearly states the action: 'Move an email to a custom folder (Folders/<name>).' It also distinguishes from the sibling tool 'move_to_label' by specifying the path prefix 'Folders/'.

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 similarity to move_to_label, but does not explicitly state when to use this vs. alternatives. However, the detailed sourceFolder parameter description provides strong guidance on correct usage and pitfalls, which counts as usage context.

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