onedrive_move_file

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

Without annotations, the description must disclose behavior. It only says 'move or rename' but omits that it likely destroys the original file (destructive) and requires overwrite permissions. No behavioral details beyond the obvious.

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?

Extremely short, but too sparse to be functional. Conciseness is negated by under-specification; vital information is missing.

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 operation's complexity (file path, rename vs move, overwrite behavior) and no output schema or parameters, the description is completely inadequate. The agent cannot invoke this tool correctly.

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 input schema has 0 properties, but a move/rename operation requires at least source and destination parameters. The description fails to explain how to specify the file or target, making the tool unusable via definition alone.

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 action (move or rename) and resource (file in OneDrive). It distinguishes from sibling tools like onedrive_delete_file or onedrive_write_file. However, it lacks specificity about the scope or constraints.

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 (e.g., onedrive_write_file for new content, onedrive_delete_file for removal). The agent has no context for selecting this tool.

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