transfer_drive_ownership

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

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly states the operation is irreversible, the current owner becomes an editor, domain restrictions, and the effect of move_to_new_owners_root on file placement. It also describes the return value, providing comprehensive context beyond the structured 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 well-structured with a concise opening sentence, followed by key behavioral notes, and a clean Args/Returns formatting. Every sentence provides necessary information without redundancy, making it easy for an agent to quickly parse purpose, constraints, and parameters.

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 complexity (4 parameters, no annotations, no output schema), the description covers all essential aspects: what it does, constraints, parameter meanings, behavioral outcomes, and return value. It is fully self-sufficient for an agent to invoke it correctly in typical ownership-transfer scenarios.

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 provides zero description coverage (0%), so the description must fully compensate. It explicitly defines each parameter with types, required status, and meaning, including the default for move_to_new_owners_root. This adds significant semantic value beyond the bare schema.

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 opens with a specific verb and resource: 'Transfers ownership of a Google Drive file or folder to another user.' This clearly distinguishes it from sibling tools like share_drive_file or update_drive_permission, which focus on sharing or permission changes rather than ownership transfer.

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 clear context for when to use the tool by noting it is irreversible and only works within the same Google Workspace domain or for personal accounts. However, it does not explicitly name alternative tools or state 'use this instead of X', so it falls short of the highest benchmark in this dimension.

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