Move to folder

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

The description only states the core action, which is already evident from the name and annotations. It does not disclose any additional behavioral traits such as folder naming conventions, side effects of moving, or the availability of dry_run. While annotations indicate readOnly=false and destructive=false, the description adds no context beyond that.

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 a single, front-loaded sentence with no redundant words. The examples are parenthetical and do not clutter the main point.

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?

The tool has 5 parameters with 60% schema coverage and no output schema, so the description carries a significant burden. It omits mention of dry_run and uidvalidity, which are important safety features, and does not describe return behavior. While the schema details these parameters individually, the overall tool context is incomplete.

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?

The schema lacks descriptions for uid and to_folder, but the description's example destination values ('Folders/<name>', 'Archive', 'Trash') provide useful context for the to_folder parameter. However, it does not clarify uid or source folder semantics, leaving some gaps.

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 action: 'move it into another folder', using the verb 'move' with the resource 'a message'. It also gives concrete destination examples ('Folders/<name>', 'Archive', 'Trash'), which differentiates it from bulk_move by implying single-message operation.

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 implies usage for filing a message into a folder but does not explicitly state when to prefer this over alternatives like bulk_move, nor does it mention any exclusions. No guidance is given for selecting this tool over sibling tools.

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