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

With no annotations, the description carries the full behavioral burden. It discloses the mutation (move), optional rename, and same-account restriction, but does not mention permission requirements, effects on shared links or permissions, or failure behavior. Basic behavior is clear, but side effects are not.

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 a single sentence that front-loads the verb and resource, includes the key optional behavior, and contains no filler or redundant information.

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?

This is a mutation tool with no annotations, no output schema, and only 25% schema coverage. The description leaves parameter semantics mostly implicit, omits return or error behavior, and does not address permissions or side effects. For an agent to call this correctly, more context is needed.

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 only 25%, so the description must compensate. It partially does by indicating itemId refers to a file or folder, destinationFolderId is a parent folder, and newName is optional for renaming. However, it does not explain ID formats, how to obtain them, or the relationship between newName and the move operation.

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 a specific verb ('Move'), resource ('Google Drive file or folder'), and destination ('different parent folder'), while also noting the optional rename capability and same-account scope. This clearly differentiates it from siblings like move_onedrive_item and rename_gdrive_item.

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 implies when to use this tool by specifying Google Drive and same-account movement, but it does not explicitly mention alternatives such as rename_gdrive_item for rename-only operations or move_onedrive_item for OneDrive. The 'within one account' phrase is the only explicit exclusion.

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