Move Folder

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

With no annotations provided, the description carries full burden. It discloses that the entire subtree is moved, parent folders are auto-created, and moving into own subtree is rejected. These are critical behavioral traits for a move operation. It does not discuss auth needs or rate limits, but the core behaviors are well covered.

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 two sentences, front-loading the primary action and then specifying key behaviors. No extraneous information or repetition.

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?

No output schema exists, but the description covers the input semantics and constraints (auto-create, subtree move). It might lack return value details, but for a move operation this is acceptable. Overall, it provides sufficient context for correct invocation.

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% (both parameters described). The description adds meaning beyond the schema: new_parent_path '' or omitted means root, and parent folders are auto-created. This provides concrete usage guidance not present in the schema.

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 a folder'), the resource ('folder'), and the scope ('whole subtree: documents, versions, annotations'). This distinguishes it from siblings like rename_folder (rename only) and delete_folder (destructive).

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 clear context: new_parent_path semantics ('' or omitted moves to root), auto-creation of parent folders, and rejection of moving into own subtree. It lacks explicit comparison to alternatives like move_markdown for individual documents, but the sibling list makes this inferable.

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