tg_mute

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

No annotations are provided, so the description carries the full burden. It discloses the default behavior (indefinite mute) and the unmute option, implying reversibility. However, it does not explain what muting actually does (e.g., silences notifications, hides the chat) or whether any permissions are required. This is some context, but not rich.

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, clear sentence that front-loads the action and key details. No wasted words; every word contributes to understanding the tool's purpose and options.

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 tool with an output schema (so return values need not be described), the description covers the main behavior, default, and unmute option. It lacks edge-case explanations (e.g., hours=0 or negative) but is sufficiently complete for typical 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 explains 'N hours' and 'default: indefinitely' (which maps to the null default of the 'hours' parameter), and 'or unmute it' maps to the 'unmute' boolean. The 'chat' parameter is not explicitly described but is obvious from the name and the description.

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 tool's function: 'Mute a chat for N hours (default: indefinitely), or unmute it.' It uses specific verbs ('mute', 'unmute') and a specific resource ('chat'), and it distinguishes from siblings like tg_alert, tg_notify, and tg_block by focusing on the mute/unmute action.

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 implies when to use the tool (when you want to mute or unmute a chat), but it does not explicitly state alternatives, exclusions, or prerequisites. There is no mention of when to prefer this over tg_alert or tg_notify, so guidance is minimal but not absent.

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