mute_dialog

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

The description explains behavioral effects of each mute parameter, such as mute_until_unix semantics (None = forever, 2^31) and what show_previews, silent, and stories_muted control. This adds significant context beyond the annotations, which only indicate a mutable, non-idempotent operation.

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 concise: one purpose sentence followed by a compact argument list. Each parameter is described in a single line with no redundant text. The structure is well-organized and front-loaded with the core purpose.

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 tool has 5 parameters and an output schema, and the description covers the core action plus all parameters. It omits explicit return-value details, but the output schema fills that gap. It lacks edge-case or permission information, but is adequate for a straightforward mute operation.

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 has no parameter descriptions (0% coverage), so the description is the sole source of meaning. It provides clear explanations for all four mute-related parameters, covering defaults and edge cases. The 'chat' parameter is self-evident from its name and required status.

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 opens with 'Замьютить уведомления чата' ('Mute chat notifications'), a specific verb+resource statement that clearly conveys the tool's function. It distinguishes from siblings like unmute_dialog and mark_read by explicitly focusing on muting notifications.

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 by the purpose and the parameter descriptions, but there is no explicit guidance on when to use this tool compared to alternatives like unmute_dialog or archive_dialog. No exclusions or alternative-tool mentions are provided.

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