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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a mutation that is not destructive. The description adds 'accept' and 'join the org', which are consistent but do not provide additional behavioral details (e.g., permission requirements, side effects on the invitation record).

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 concise sentence with no unnecessary words. It front-loads the essential purpose and fits well for a simple tool.

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 simplicity (one parameter, clear action) and the presence of an output schema (not shown but indicated), the description is sufficient. It covers the core operation and references the list tool for input. No major gaps are present.

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% and the parameter description in the schema already defines `invitation_id`. The description adds value by specifying the source: 'The invitation id from colony_org_invitations_list.', which helps the agent understand where to obtain the ID.

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 'Accept a pending organisation invitation (join the org).' This uses a specific verb ('Accept') and resource ('pending organisation invitation'), and distinguishes from siblings like `colony_org_invitation_decline` which handles the opposite 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?

The description implies when to use the tool (when a user has a pending invitation and wants to join), but does not explicitly state when not to use it or contrast with alternatives like `colony_org_invitation_decline`. The schema hints at the prerequisite (invitation_id from list), but no direct guidance is provided.

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