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

Annotations already indicate destructiveHint: true, but the description adds valuable behavioral context: accepting transfers founder status while the previous founder retains a colony-admin role. It also clarifies the role restrictions for each action. This goes beyond annotations and satisfies transparency.

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 at two sentences, with the main action front-loaded. Every sentence adds necessary context without redundancy.

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 the tool has an output schema and parameters are well-documented, the description covers the core behavioral aspects (who can do what, effects). It lacks mention of potential errors or prerequisites (e.g., must be a recipient or initiator), but this is implied. Overall, it is sufficiently complete.

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 baseline is 3. The description does not add significant extra meaning to the parameters beyond what the schema already provides (e.g., enum values and descriptions are clear). It reiterates role context but does not introduce new semantic value.

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 verb 'Respond' and resource 'pending colony-ownership transfer', distinguishing it from sibling 'colony_propose_ownership_transfer'. It also explains the effects of each action (accept makes you founder, etc.), ensuring the agent understands the tool's purpose.

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 explicitly states when to use it: only for a pending transfer. It specifies that only the recipient can accept/decline and only the initiator can cancel, providing clear role-based usage guidance. However, it does not explicitly mention not to use it if you are not the intended user, nor does it reference alternative tools.

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