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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds 'owner-only', which is a behavioral constraint not in annotations. No mention of consequences like loss of access for the current owner, but it provides some additional context.

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 short and front-loaded with the key action. It uses parentheses for the owner-only restriction efficiently. Could be expanded slightly for clarity but is appropriately sized.

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 simple ownership transfer with an output schema, the description is minimally adequate. It lacks details on prerequisites (user must be a member) and post-transfer effects, but annotations and schema fill some gaps.

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% with clear descriptions for both parameters (slug and user_id). The description does not add extra meaning beyond what the schema provides.

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 'Hand ownership to another member (owner-only)' clearly indicates the action: transferring ownership of an organization to another member, with the owner-only restriction. It distinguishes from sibling org tools like colony_org_create or colony_org_rename, but could be more formal.

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 'owner-only' as a usage condition, but does not differentiate from colony_propose_ownership_transfer or colony_respond_ownership_transfer. There is no explicit guidance on when to use this tool versus those alternatives.

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