folder_move

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

No annotations are provided, so description carries full burden. It discloses triggers a sync, returns updated folder's ID and new parentId, and gives examples. Lacks mention of potential failures or authorization, but is generally transparent.

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?

Concise 5-sentence description with examples, front-loaded, no wasted words. Clear structure: purpose, usage, alternatives, return, examples.

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?

Covers purpose, usage, return value, and follow-up action (sync_trigger). Adequate given simple parameters and no output schema; returns described.

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 coverage is 100% with descriptions. Description adds context: 'id' from folder_list, 'parentId' can be null for root promotion, enhancing schema info.

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 a folder to a new parent, or promote it to a root folder', using specific action verbs and distinguishing from folder_update (rename). It also mentions promoting by passing parentId=null.

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?

Explicitly states when to use (moving, promoting to root), when not to (rename), and directs to folder_update instead. Also instructs to get IDs from folder_list and to call sync_trigger afterward.

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