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

Annotations already declare that this is a non-read-only, non-destructive, idempotent, closed-world operation. The description adds useful context by specifying the resulting state ('Open') and timing ('now'), but it does not cover permissions, side effects, or failure modes beyond what the annotations imply.

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, front-loaded sentence with zero wasted words. It immediately conveys the action and outcome without any filler.

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?

Given the low complexity (one parameter, no output schema) and rich structured data (full schema coverage and annotations covering safety), the description is nearly sufficient. It states the core effect clearly, though it could note that the conversation must currently be snoozed to avoid errors.

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 100% and the single parameter conversationId is fully documented in the schema as coming from list_conversations. The description adds no additional meaning, format, or syntax beyond what the schema already provides.

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 states a specific verb ('bring back') and resource ('snoozed conversation') with a clear target state ('Open now'). It is easily distinguishable from the opposite sibling snooze_conversation, but it does not explicitly name or differentiate from other similar siblings like restore_conversation or reopen_gap.

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 phrase 'a snoozed conversation' implies the condition for use, giving implicit guidance that this tool applies to conversations currently in a snoozed state. However, it provides no explicit when-to-use instructions, prerequisites, or alternatives to consider.

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