drive_permissions_transferOwnership

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

Annotations already indicate destructiveHint=true and idempotentHint=false, and the description greatly enriches this by disclosing the immediate ownership change, downgrade of the current owner to writer, unavoidable notification email, and lack of an acceptance step. It also explains the shared-drive exclusion with rationale.

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 packed with decision-relevant details and wastes no sentences. It front-loads the core behavior, then covers exclusions, side effects, and the sibling alternative in a logical order.

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, non-idempotent operation with no output schema, the description covers the essential behavioral context: immediate effect, recipient notification, scope limitations, and alternative routes. It does not describe the exact response shape, but that is less critical given the transfer semantics are thoroughly disclosed.

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 the schema already documents all four parameters. The description reinforces fileId and emailAddress constraints (same organization, My Drive only) but does not add new semantics for fields or moveToNewOwnersRoot beyond what the schema states.

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 and resource: immediately transfer ownership of a file to another Google Workspace account in the same organization. It also clearly distinguishes this from drive_permissions_proposeOwnershipTransfer by naming the alternative and contrasting immediate vs. acceptance-required 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 gives explicit when-to-use and when-not-to-use guidance: only for files in "My Drive," only within the same organization, and not for shared drives. It also explicitly redirects to drive_permissions_proposeOwnershipTransfer for personal/consumer Google account transfers, leaving no ambiguity about selecting the right sibling tool.

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