rename_drive_item

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds context: it renames in the current folder, is idempotent when title unchanged, and fails on sibling collisions. This goes beyond annotations but could mention that the operation modifies the item's title (non-destructive). 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?

Three sentences, front-loaded with the main purpose. Each sentence adds essential information: rename action, idempotency, and collision/alternative guidance. No fluff.

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 output schema exists, the description covers rename behavior, idempotency, and collisions. However, it does not explain the mutual exclusivity of path and itemId (schema 'not' constraint) or the drive parameter, which could lead to user errors. Mostly complete but has minor gaps.

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 description coverage is 100% but parameter descriptions are minimal ('a string that will be trimmed'). The description does not elaborate on parameters like drive, path, itemId, or their constraints (e.g., mutual exclusivity). Baseline is 3 since coverage is high, but the description adds little parameter meaning.

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 verb 'Rename' and the resource 'Drive item (file or folder)', and distinguishes from the sibling tool 'move_drive_item' by noting that this tool only renames within the current folder. This provides specific purpose and differentiation.

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 explicitly states when to use (rename in current folder), when not to (use move_drive_item to change folders), and provides idempotency behavior and collision rejection. This gives clear guidance on usage context and alternatives.

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