Mute or unmute a chat

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

Annotations already establish that the operation is mutable, idempotent, and not destructive, so the description does not need to repeat that. It adds the behavioral nuance that muting can be temporary or indefinite until unmuted. It does not disclose additional side effects or permissions, but none are clearly required for this simple setting.

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 compact sentence that front-loads the action and includes the key duration and unmute semantics. No words are wasted, and it is appropriately sized for the tool's simplicity.

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?

Combined with the rich parameter descriptions and annotations, the description makes the tool fully invokable: the agent knows what account to use, what chat identifier formats are accepted, and how duration and muted interact. There is no output schema, but for a straightforward mutation this is not a critical gap.

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 schema already explains accountId, chatId, durationSeconds, and muted well. The description adds only the explicit `muted: false` unmute hint, which is a minor overlay on the schema rather than substantial new meaning.

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: muting or unmuting a chat's notifications. This distinguishes it from sibling tools like archive_chat or pin_chat, which affect chat visibility or ordering rather than notification behavior. It does not explicitly name or contrast siblings, so it stops short of a 5.

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 gives useful operational guidance: mute for a duration or until unmuted, and unmute with `muted: false`. However, it does not explicitly say when to choose this tool over alternatives such as archive_chat, pin_chat, or mark_chat_read, so usage context is mostly implied.

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