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 agent knows this is a mutation. The description adds that both move and rename can be done in one request. However, it does not disclose what happens to the original item (moved/renamed, not duplicated) or any permission requirements. With annotations covering the safety profile, the description provides marginal 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 brief (two sentences), but the first sentence 'Update the navigation property items in drives' is unnecessary and potentially confusing. The tip is useful. Some trimming would improve clarity without losing 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?

Given the tool's complexity (destructive operation with many parameters) and no output schema, the description should explain return values, irreversibility, or the need for confirmation. The confirm parameter is documented in schema, but the description doesn't mention it. The tip is helpful but insufficient for complete understanding of context.

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 schema documents most parameters. The tip adds semantic guidance: 'parentReference' for move, 'name' for rename. The confirm and driveId/driveItemId parameters are described in the schema. However, the body parameter has many nested properties, and the description does not clarify which are relevant for this operation, limiting added value.

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 title and tip clearly indicate move/rename operations. The initial description 'Update the navigation property items in drives' is vague, but the tip explains the actual purpose: moving and/or renaming files or folders. This distinguishes it from sibling tools like copy-drive-item or delete-onedrive-file.

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 basic guidance on when to use: provide parentReference for move, new name for rename, or both. However, it lacks explicit directions on when not to use this tool vs alternatives (e.g., copy-drive-item for duplication). No prerequisites or constraints are mentioned.

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