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

The description discloses the key behavioral side effects beyond the readOnlyHint=false annotation: it moves the file, optionally renames it, and creates the destination folder if missing. It does not mention overwrite behavior or what happens when a file with the same name exists, but the main mutation semantics are clear.

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 compact: one sentence defines the action and effects, and a second provides concrete usage triggers. Every part earns its place, with no fluff or repetition of schema details.

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 simple three-parameter move tool with no output schema, the description covers the essential aspects: target path semantics, optional rename, side-effect of folder creation, and when to invoke it. It omits overwrite and return-value details, but those are not critical for a 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 description coverage is 100%, so parameters are already well documented. The description adds only minor reinforcement by mentioning 'optionally renaming' for new_name and 'Creates the folder if it doesn't exist' for to_path, but no meaningful new parameter-level information.

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 and resource: 'Move one of the user's files ... into a folder of their file storage,' with optional renaming and folder creation. It is more specific than many siblings like octopus_make_folder or octopus_list, though it does not explicitly differentiate itself from octopus_move.

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?

It gives explicit trigger phrases: 'Use when the user says save / put / move / file this into a folder.' However, it does not state when not to use it or mention alternatives such as octopus_move, so it lacks explicit exclusion guidance.

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