anythingllm_move_files

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is clear. The description adds context on the required path format but does not explicitly disclose side effects like the original path being removed. 'Move' implies this, but there's no additional behavioral detail beyond annotations.

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 organized with a clear purpose, explanation, and args section. There is some redundancy between the first paragraph and the Args block, both stating the 'from'/'to' requirement, but it remains concise and readable overall.

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?

With an output schema present, return values are covered. The tool has a single parameter and simple logic; the description explains the input format thoroughly. Minor missing details like folder creation behavior are not critical for basic usage, making it fairly complete.

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 0%—the schema only defines an array of objects without key details. The description fully compensates by specifying each entry must have 'from' and 'to' keys, providing an example, and referencing list_documents paths. This adds complete meaning 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 states a specific verb and resource: 'Move documents between folders.' This clearly differentiates from sibling tools like upload_file_to_folder or remove_documents. The example further clarifies the operation, and the path format reference adds precision.

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 clearly indicates the operation type ('Move documents between folders') and the required path format, which sets clear context. However, it does not explicitly mention when not to use it or name alternatives, so there is no exclusion guidance.

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