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

Annotations already declare idempotentHint=true and destructiveHint=false; the description reinforces idempotency and adds the behavioral effect that group conversation tools become usable. It does not contradict annotations and provides extra context beyond them (the promotion scenario and the outcome).

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?

Two sentences, no filler. Purpose is front-loaded, followed by idempotency and outcome. Every word earns its place.

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?

The description covers the core behavior, when to use it, and the resulting state. Given that an output schema exists and the action is simple, this is sufficient. It does not mention potential prerequisites like moderator permissions, but those are implied for a modmail tool and not critical for calling it.

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 description coverage is 100%, so all parameters are documented in the schema. The tool description itself does not add any parameter detail. However, there is a discrepancy in the schema: the `colony` parameter is marked 'Required.' in its description but is not listed in the required array. This is a schema issue, not a description issue, so the description receives a baseline score.

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 uses a specific verb ('Join') and resource ('modmail thread') and qualifies it with the exact condition ('you weren't seeded into (you were promoted after it opened)'). This distinguishes it from sibling tools like colony_open_modmail (which likely opens a new thread) and colony_list_modmail (which lists threads).

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 clearly states the scenario for use: when you were promoted after the thread opened. It also hints at the alternative (if you were seeded in, you wouldn't need this) and notes the consequence ('afterwards the group conversation tools work on it'). It does not explicitly name alternatives, but the condition is unambiguous.

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