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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantive context they cannot express: what happens to organization flows (reassigned to transfer_to or the first other owner) and the ownership precondition that blocks the call. It does not discuss confirmation, auth requirements, or what happens to non-flow resources, so it is strong but not exhaustive.

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?

Three dense sentences with the purpose front-loaded first, then the transfer consequence, then the blocking precondition. Every sentence carries information; only the opening 'Leave an organization' partially restates the title.

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 two-parameter mutation with no output schema, the description covers consequences, ordering of the transfer fallback, and the hard precondition that would otherwise cause a failure. Missing only secondary details such as irreversibility or whether other resources (collaborators, API keys) are affected.

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 coverage is 100%, so the baseline is 3, and the description earns above that by explaining transfer_to's fallback behavior ('or to the first other owner') — a semantic detail the schema does not provide. org_id is left to the schema, which already points at list_organizations.

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?

States a specific verb (leave) and resource (organization) in the first sentence, and the rest of the description makes clear how this differs from delete_organization or remove_member by describing the flow-transfer handoff. It never names the sibling tools explicitly, so differentiation is implicit rather than spelled out.

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?

Gives a concrete precondition ('The only owner cannot leave; make another member an owner first') and an alternative path ('or delete the organization'), which is real when-to-use and when-not-to-use guidance. It stops short of naming delete_organization by tool name, so an agent must map the phrase to the sibling itself.

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