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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful scope information about which channels are aggregated, but says nothing about ordering, pagination, volume limits, or whether empty threads appear — meaningful gaps for a list operation with no output schema.

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?

A single short sentence with no padding, and the channel scope is front-loaded. It is slightly clipped — a fragment rather than a full statement of action — but it wastes no words.

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?

With no parameters, no output schema, and annotations covering safety, the description only needed to define the return shape and scope. It does neither: an agent cannot tell whether the result is a flat conversation list, threads with last message, or unread counts, or whether pagination applies. Adequate but incomplete for a listing endpoint.

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 tool takes zero parameters, so there is no parameter semantics for the description to elaborate. Baseline 4 applies; nothing is missing or contradicted on this dimension.

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 names the resource and enumerates the channels covered (SMS, WhatsApp, Telegram inbound, outbound email), which helps distinguish it from send_* tools. However, the verb is only implied by the name/title — the sentence never states that this lists or retrieves conversations, so it reads more like a content label than an action definition.

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?

There is no guidance on when to call this versus the obvious siblings get_conversation (single thread), send_conversation_message, or save_conversation. It also does not say whether it returns all conversations or a filtered subset, leaving the agent to infer the entry point.

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