transfer_drive_ownership

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

With no annotations, the description fully discloses key behaviors: irreversibility, role change (current owner becomes editor), domain restrictions, and the effect of parameters like dry_run for preview. This is comprehensive beyond the input schema.

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 efficiently structured with a clear purpose sentence, behavioral notes, parameter list, and return description. It is front-loaded and each part serves a purpose without redundancy.

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 ownership transfer complexity, no annotations, and presence of an output schema, the description covers all necessary aspects: purpose, behavioral traits, parameter semantics, constraints, and return value. It is fully complete for an agent to select and invoke correctly.

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 description explains all 5 parameters, including their roles, required status, defaults, and effects (e.g., move_to_new_owners_root moves file to new owner's root; dry_run provides preview). This compensates for the 0% schema description coverage.

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 'transfers' and the resource 'ownership of a Google Drive file or folder'. It distinguishes from sibling tools like 'share_drive_file' by focusing on ownership transfer rather than sharing permissions.

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 specifies domain restrictions ('Only works within the same Google Workspace domain or for personal accounts') and notes irreversibility, providing context for when to use. However, it does not explicitly name alternatives or when not to use, such as suggesting 'share_drive_file' for non-ownership sharing.

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