move_folder_tool

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

Discloses that the tool moves folder and contents, returns move status with counts, and warns about circular references. However, lacks details on overwriting behavior, error scenarios, or any side effects beyond what is stated.

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 and well-structured: a purpose statement, bullet lists for usage and non-usage, and a returns line. Every sentence adds value without redundancy.

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 the main aspects of the tool's behavior and usage, including return value. Could mention what happens on conflict (e.g., if destination exists), but given no output schema, it provides sufficient context for a folder move tool.

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 high (75%) with parameter descriptions and examples already provided. The tool description adds the circular reference warning but does not significantly extend parameter semantics beyond 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 verb 'move' and the resource 'entire folder and all its contents', distinguishing it from sibling tool move_note_tool which moves individual notes.

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 lists when to use (reorganizing, archiving, consolidating, seasonal) and when NOT to use (moving individual notes, moving to subfolder causing circular reference), with a direct alternative mentioned (use move_note).

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