Mute a peer

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

The description adds the key behavioral detail that without `untilDate` the mute is permanent, going beyond the annotations (`idempotentHint`, `openWorldHint`). It does not contradict annotations, but it does not disclose potential side effects or return behavior.

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 two short sentences, front-loads the primary action, and contains no outright redundancy. Every word contributes meaning.

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 3-parameter tool with annotations and no output schema, the description covers the core action and the main optional parameter behavior. Lacks explanation of `accountId`, but it is optional and a common pattern, so the description is complete enough for straightforward use.

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 0%, so the description must compensate. It only clarifies the role of `untilDate` ("mutes forever" without it), leaving `peer` and `accountId` unexplained. This is partial compensation but insufficient for two other parameters.

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 explicitly states the verb and resource: "Mute a chat". It distinguishes from the sibling tool `unmute_peer` by focusing on muting, and clarifies the behavior with `untilDate` (forever if omitted).

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?

Usage is implied from the title and description—use it to mute a chat. However, no explicit guidance is given on when to prefer this over alternatives like `unmute_peer` or `set_notify_settings`, and no exclusions are mentioned.

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