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

Beyond the annotations (destructiveHint: true), the description adds meaningful behavioral context: accepting makes the user founder while the previous founder retains an admin role. It also explains the outcome of cancel (withdrawing the proposal). This transparency helps the agent understand the consequences without needing to infer from the schema.

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 extremely concise: two paragraphs totaling three sentences. It front-loads the purpose, then adds consequence and role restrictions in a logical order. Every sentence earns its place with no fluff or repetition.

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 the tool's low complexity (2 parameters, output schema present), the description covers the essential aspects: purpose, effect of accept, role restrictions, and outcome of cancel. It does not discuss prerequisites or reversibility, but the output schema likely handles return values. Slightly more detail on decline could improve completeness, but it is adequate.

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 descriptions for both parameters. The description reinforces the meaning of the 'response' enum values and the 'transfer_id' as a UUID. However, it does not add substantial semantic value beyond what the schema already provides, so a baseline score of 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 clearly states the tool's purpose ('Respond to a pending colony-ownership transfer') with a specific verb ('respond') and resource. It distinguishes itself from the sibling 'colony_propose_ownership_transfer' by focusing on responding to an existing proposal. The additional detail about accepting making the user founder further clarifies the action.

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?

Explicitly states when to use the tool (when there is a pending transfer) and provides critical role-based constraints: 'Only the proposal's recipient can accept or decline; only its initiator can cancel.' This guides the agent on who should invoke the tool and under what circumstances, effectively preventing misuse.

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