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

Annotations are all false but the description adds important behavioral traits: ownership requirement, rejection of team targets, and immutability of handle stamps on prior versions per VISION 14. This goes beyond what annotations provide.

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 very concise, using three short sentences that each add unique value. It is front-loaded with the core action and includes key constraints without unnecessary detail.

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 that an output schema exists (not shown), the description covers all essential aspects: action, identification, ownership restriction, invalid targets, and a behavioral note about immutability. It is complete for a transfer operation.

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 fully describes both parameters. The description restates identification methods (UUID, @handle/slug, email) but does not add new meaning beyond the 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 clearly states the action (transfer template ownership) and identifies the resource (template). It specifies identification by UUID or @handle/slug and notes 'Owner only', which distinguishes it from sibling transfer tools like transfer_workflow_ownership and transfer_team_ownership.

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?

It explicitly states 'Owner only' and 'Team targets are rejected', providing clear context on when to use and what inputs are invalid. While it doesn't name alternatives, the sibling list implies other transfer tools exist for different cases.

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