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

The description clarifies that the operation clears two specific fields (`is_muted`, `muted_until`) and is idempotent, complementing the annotations. It avoids repeating readOnlyHint and destructiveHint (which are false) and adds the per-participant scope.

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 with only two short sentences, front-loading the purpose and including a key behavioral trait (idempotency). 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?

For a simple one-parameter tool with full schema coverage and an output schema, the description covers the core action and idempotency. It could optionally mention that it resets mute status to default, but the behavioral information is sufficient.

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?

The input schema already describes `conversation_id` as 'UUID of the group' with 100% coverage. The description adds minimal extra semantic value by linking the parameter to the group context, but does not provide format or usage details beyond the 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 uses a specific verb 'Clear' and identifies the exact fields (`is_muted`, `muted_until`) and scope ('caller's participant row'), making the purpose unambiguous. The sibling `colony_mute_group_conversation` is implicitly contrasted.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., `colony_mute_group_conversation`). The usage is implicitly clear from the name, but the description lacks usage context.

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