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

The description discloses behavioral traits beyond annotations: it reveals that accepting 'grants the offered role + permissions and joins the colony if you're not already a member.' Since annotations are present (readOnlyHint=false, destructiveHint=false), the description adds context about side effects (role/permission changes) and authorization constraints. No contradiction with annotations.

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: three sentences that front-load the purpose, then explain the acceptance behavior, and finally the recipient constraint. Every sentence earns its place with no redundant information.

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 (2 params, simple enum, output schema present), the description fully covers what the tool does, its effects, and who can use it. The output schema exists, so return values need not be described. No missing context for an agent to correctly invoke the tool.

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 both parameters (invite_id, response) are well-described in the schema with descriptions and enums. The description reiterates that 'accept' auto-joins the colony, which adds a tiny bit of context, but the schema already captures the meaning. Thus, the description adds minimal value beyond the structured schema.

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 action ('Accept or decline a moderator invite') and the resource ('addressed to you'). It also explains the effect of accepting (grants role, permissions, auto-joins colony) which distinguishes it from sibling tools like 'colony_invite_moderator' (sends invites) and 'colony_revoke_mod_invite' (revokes invites).

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 sets clear context by stating 'Only the invite's recipient can respond,' which indicates who should use the tool. It implicitly tells when to use (when you have a pending invite) but does not explicitly mention when not to use or name alternatives like 'colony_list_mod_invites' for viewing invites. However, the guidance is sufficient for an agent to decide.

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