move-rename-onedrive-item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is established. The description adds the detail that move and rename can be combined and specifies how to set them, but it does not disclose potential failure modes (e.g., conflicts) or side effects. Given the annotations, this is acceptable but not rich.

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?

Concise: one clear sentence plus a compact tip. The core purpose is front-loaded, and the instruction is efficient without filler. Every sentence earns its place.

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 destructive operation with no output schema, the description covers the main usage patterns but does not mention the confirm parameter (though described in schema) or what happens on success. It is adequate for an agent to call correctly, but slightly incomplete for a comprehensive understanding.

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 description clarifies the operational meaning of body.parentReference (for moving) and body.name (for renaming), which is not explicit in the schema. With 83% schema coverage, the schema already documents the properties, but this guidance adds value by linking them to the intended actions.

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 states 'Move or rename a OneDrive item' with a specific verb and resource, and the tip clarifies that it handles move, rename, or both. This clearly distinguishes it from sibling tools like copy-drive-item or delete-onedrive-file, making its purpose unambiguous.

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?

Explicitly instructs how to perform each operation: 'To move, provide parentReference with the target folder's id. To rename, provide a new name.' It also notes both can be done in a single request. It does not explicitly mention alternatives or when not to use, but the guidance is clear and contextual for this tool's intended scenarios.

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