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

Annotations only indicate the tool is not read-only, so the description carries the burden for conveying mutation effects. It usefully discloses a non-obvious consequence: the transferring owner stays on as an admin, preventing an assumption that they are removed. It does not cover reversibility or downstream permission impacts, but this is solid given annotation coverage.

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 a single front-loaded sentence with no filler. Every phrase—'active member,' 'owner only,' and 'stay on as an admin'—adds meaningful operational context.

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 high-stakes ownership mutation, the description covers who may call it, who receives ownership, and the caller's resulting role. With complete schema parameter descriptions and an output schema present, no critical invocation detail is missing; the only minor omission is explicit guidance about the slug/org_id identifier alternatives, which the schema already documents.

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 parameters are already well documented: slug and org_id are alternative organization identifiers, and user_id is sourced from findagent_list_members. The description adds no extra parameter-level meaning beyond confirming the transfer direction, so the baseline 3 is appropriate.

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-resource pair ('Transfer ownership of an organization') and specifies the recipient ('another active member') plus a key precondition ('owner only'). This clearly differentiates it from role-management siblings like change_member_role or remove_member.

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 states who is allowed to use it ('owner only') and the required target state ('active member'), which implies valid usage. However, it gives no explicit guidance on when to prefer this tool over the closely related findagent_change_member_role or when it should not be used.

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