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

With no annotations, the description carries the behavioral burden. It discloses ordering, default page size, response shape, cursor behavior, endpoint equivalence, and that it is free. It does not mention auth/error behavior, but for a read-only listing tool this is a strong disclosure.

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 compact and front-loaded with the key behavior, then pagination, response shape, and follow-up. A few extras like 'Free' and 'Same shape as GET /v1/conversations' are minor but relevant, so nothing feels wasted.

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?

Output schema exists, so return value details are already structurally documented. The description covers the main operational concerns: sort order, limit, cursor pagination, and next step. The missing api_key guidance is the main completeness gap.

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 33%, but the description adds cursor semantics ('pass next_cursor back as cursor') and restates the limit range. The api_key parameter remains entirely undocumented in both the schema description and prose, which is a notable gap.

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 clearly identifies the resource (chat conversations) and the operation (listing them), and adds pagination and field details. It also distinguishes this from the sibling get_conversation by naming it as the next step.

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 provides clear context: use this for paginated listing of conversations, with cursor-based traversal for more results, and directs the agent to get_conversation next. It does not list explicit exclusions, but the sibling relationship is sufficiently clear.

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