move_folder

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

Annotations already provide readOnlyHint=false, destructiveHint=false, so the safety profile is known. The description adds useful behavioral context: the folder's contents move along with it, and system folders cannot be moved, which goes beyond the annotation hints and helps the agent predict side 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?

The description is brief and well-structured: a topic sentence, a key behavior, a usage guideline, a limitation, and a clear Args list. Every sentence adds value with no redundancy, and the most important information is front-loaded.

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?

For a tool with two parameters, the description covers purpose, behavior, usage guidance, and parameter semantics. An output schema exists, so return value details are not required in the description. The tool's scope and limitations are adequately described, making it complete for an agent to select and invoke correctly.

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 input schema provides only types and requiredness, but the description's Args section gives full semantics: `folder` can be a name or full path with an example, and `parent` is optional with default behavior (moves to top level). This fully compensates for the 0% schema description 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 states a clear action ('Moves a folder under another parent') with a specific resource, and distinguishes from siblings by noting it moves the whole folder tree rather than individual messages. The limitation about system folders further clarifies scope.

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 explicitly advises using this tool when moving a whole folder instead of moving many emails one by one, giving a clear when-to-use context and an implicit alternative. It also states a system folder exclusion, though it does not name the sibling tool for moving individual messages.

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