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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavior (result ordering 'newest first') but says nothing about result volume, default page size, or pagination behavior, which is the main thing an agent would want to know here.

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?

Two sentences, zero filler, with the resource and ordering front-loaded before the filter options. Every clause maps to a real capability of the tool.

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 six parameters, no output schema, and a pagination cursor, yet the description never mentions paging or what a returned conversation contains. Adequate for identification, but thin for actually driving the call correctly on a multi-page listing.

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 83%, so the schema carries most of the load and baseline 3 applies. The description mentions the channel, unanswered, and text filters but adds no precision beyond the schema — in fact the schema's only_unanswered description ('website and voice conversations where the agent failed to answer at least once') is more exact than the prose. limit, cursor, and agent_id are never mentioned.

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?

States a specific verb and resource ('List recent customer conversations') plus the scope (website widget, voice, messaging channels) and ordering ('newest first'), which separates it from the singular get_conversation. It does not explicitly name the sibling tools it should be preferred over, so it stops short of a 5.

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 second sentence hints at narrowing by channel, unanswered status, or text, which implies use cases but never states when to choose this over get_conversation, list_unanswered_questions, or list_leads. No exclusions or prerequisites are given.

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