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

Annotations only declare destructiveHint=true and readOnlyHint=false; the description goes further by disclosing per-file partial-failure semantics (each file answered on its own with ok true or ok false plus reason), that content and sharing are preserved, and that files not owned by the member or outside their shared drives return ok false. It does not mention rate limits or whether any rollback is possible after a partial move.

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?

Four tight sentences with the action and scope front-loaded, followed by result semantics and then the permission constraint. No filler, no repetition of the title, and every clause carries information the agent needs.

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, open-world batch mutation with no output schema, the description supplies the essential context: batch limit, per-item success/failure reporting, data-preservation guarantees, and authorization constraints. Minor gaps remain around dry_run behavior and how the person/project execution context affects outcomes.

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%, so all six parameters including person, dry_run, project, and to_folder_name are already documented. The description restates the 100-item cap and the search_google_drive provenance of file_ids, both of which the schema already carries, so it adds little meaning beyond the structured fields.

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?

States a specific verb (move) and resource (files or folders in the connected Google Drive) with clear scope: into a single destination folder, up to 100 per call. This cleanly separates it from sibling tools like copy_google_drive_file, trash_google_drive_files, and restore_google_drive_files without the agent needing to inspect schemas.

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 routes the agent for inputs: file_ids come from search_google_drive, and the schema adds that create_google_drive_folder should be used if the destination does not exist. It does not state when to prefer this over copy or trash, nor does it explain the dry_run preview path, which is left entirely to the schema.

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