drive_move

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

Beyond the annotation (destructiveHint=false), the description discloses authentication requirement, failure conditions (destination occupied or parent missing), and clarifies there is no copy operation. This adds significant behavioral context.

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 concise (4 sentences) and well-structured: purpose, rename vs move, failure conditions, exclusions. Every sentence adds essential information 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?

Given the tool's complexity (two string parameters, no output schema), the description fully covers usage, constraints, and edge cases. It answers likely questions about what happens on failure and how to accomplish related tasks (rename vs move).

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?

The schema has 100% coverage with descriptions of both parameters. The description adds value by explaining the semantics of rename vs move in terms of the parameters, including an example. This goes beyond the schema's definitions.

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 explicitly states 'Move or rename a file or folder on Proton Drive', providing a clear verb and resource. It also distinguishes from siblings by warning against using for copy (no copy operation) or download (use drive_download).

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 explains when to use move vs rename (keep same parent vs different parent). It also provides explicit exclusions: 'Do not use to copy a file... or to download to local storage (use drive_download).' This gives clear guidance on alternatives.

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