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

Beyond the annotations, it discloses the 10-minute clamp behavior (a later time is silently cut to 10 minutes) and the retry/idempotency-key contract, which an agent cannot infer from the schema alone. It does not say whether the mute can be undone (unsnooze_conversation exists as a sibling), leaving one behavioral gap.

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?

Four tight sentences, front-loaded with the core action and its hard limit before the alternative and retry advice. The 'note is optional' clause is the only near-filler; the rest 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 non-destructive, idempotent mutation with no output schema, the definition covers the critical semantics: time cap, clamping, optional note, alternative tool, and retry key. What remains is minor (reversibility path, success response shape), which the annotations already partly cover.

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 only 25%, so the description carries real weight here: it explains that snoozed_until must be ISO 8601 and in the future and gets clamped at 10 minutes, and that note is optional. conversation_id is never described beyond being implied by 'a conversation', and the note's purpose (max 500 chars) is unelaborated, so compensation is partial.

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 a specific verb and resource ('Mutes a conversation') and immediately names the governing parameter and its hard limit, which distinguishes it from siblings like set_conversation_reminder, snooze_task, and unsnooze_conversation.

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?

It gives a concrete usage scenario ('as the inbox's Mute does while someone is on a call') and explicitly routes later follow-ups to set_conversation_reminder. It stops short of stating when not to use it — for example, the distinction from snooze_task for tasks — so it is clear context without full exclusions.

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