move-rename-onedrive-item

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate safety. It adds the note about combining move and rename in one request, but doesn't disclose potential side effects like overwriting, path updates, or failure modes. This is minimal additional 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 two sentences, the first states the core purpose and the second is a compact tip. It is front-loaded, scannable, and every sentence contributes meaning.

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 mutation tool with a large input schema and no output schema, the description covers the essential operations (move, rename, or both) with clear parameter guidance. It could say more about error cases, cross-drive moves, or permission requirements, but the basic usage is complete enough.

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 high (83%), so the baseline is 3. The description adds value by explicitly mapping parentReference.id to the move action and 'new name' to rename, which clarifies the semantic intent beyond the schema's field descriptions.

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 starts with 'Move or rename a OneDrive item,' which clearly states the verb, resource, and operation. It distinguishes itself from siblings like copy-drive-item and delete-onedrive-file by explicitly naming move/rename rather than copy or delete.

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 gives explicit instructions: provide parentReference to move and new name to rename, and notes both can be done in a single request. It doesn't explicitly contrast with alternatives, but the usage context is clear and actionable.

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