move_drive_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention any side effects (e.g., the item is removed from its original location), permission requirements, reversibility, or return values, leaving the agent without critical operational information.

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 extremely terse, consisting of a single simple sentence. While it is concise, it is under-specified and does not provide sufficient information for an agent to correctly invoke the tool; it is more of a label than a useful description.

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?

The tool has a moderately simple operation with three parameters, no annotations, no output schema, and no parameter descriptions. The description is essentially just a label and fails to provide any context about the operation's purpose, parameter meanings, or expected behavior, making it far from complete for an agent to use effectively.

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 input schema defines three required parameters (driveId, itemId, parentId) but provides zero description coverage. The description 'Move a drive item' does not explain any of these parameters, leaving their semantics entirely ambiguous and failing to compensate for the schema's lack of 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 states the specific action 'move' and resource 'drive item', clearly indicating the tool's primary function. It distinguishes from sibling tools like copy_drive_item and delete_drive_item through the unique verb, but lacks additional context about the move's target or behavior.

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 provides no information about when to use this tool, what prerequisites exist, or how it compares to alternatives such as copy_drive_item or delete_drive_item. There is no guidance on context, exclusions, or alternative use cases.

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