move-rename-onedrive-item

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

Annotations indicate destructiveHint=true and readOnlyHint=false, confirming mutation. The description adds the specific move/rename behavior. However, it does not disclose side effects like permission preservation or rate limits. No contradiction with annotations.

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 first sentence 'Update the navigation property items in drives' is generic and redundant. The tip is concise and well-structured. Removing the first sentence would improve conciseness.

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?

No output schema. The description only covers move/rename usage, but the input schema allows updating many other properties. The tool could mislead an agent into thinking only move/rename are possible, while the schema supports setting other fields. The description should clarify that other body properties may be ignored or have no effect.

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 80%, but the description adds crucial meaning by mapping the body parameters: parentReference.id for move and name for rename. This goes beyond the schema descriptions and helps the agent correctly invoke the tool.

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 tool moves and/or renames a file or folder, with a tip explaining how. The title 'move-rename-onedrive-item' reinforces this purpose. It distinguishes from siblings like 'copy-drive-item' but does not explicitly list what it does not do.

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 tip provides explicit guidance on when to use the tool: for moving (provide parentReference.id) or renaming (provide new name), and that both can be combined. It does not mention when not to use it or offer alternatives, but the context is clear enough for an agent.

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