Move files on Proton Drive

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

Annotations indicate idempotentHint=true, but the description adds no behavioral context beyond the action. It does not disclose whether existing destinations are overwritten, permissions required, or error handling (e.g., what happens if the source file is open). The bar is low because there are no annotations beyond idempotence, but the description still fails to add significant transparency.

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?

Single sentence with zero waste. Front-loaded with the primary action. Ideal conciseness for a straightforward tool.

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?

Given no output schema and simple parameters, the description is minimal but adequate for basic understanding. However, it omits details about success/error handling, return values, or side effects (e.g., overwrite behavior). For a CLI tool, the outcome is partially implied, but more completeness would help.

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 'from' and 'to' parameters clearly described in the schema as 'Current remote path' and 'Destination remote path'. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Moves' and the resource 'remote path' using the CLI. The name 'proton_drive_move' distinguishes it from siblings like 'proton_drive_copy', but the description does not explicitly contrast them. However, the purpose is well-understood.

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?

No guidance on when to use this tool versus alternatives such as 'proton_drive_copy' or 'proton_drive_remove'. The description lacks context about prerequisites, conflicts, or scenarios where moving differs from copying or deleting.

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