list_conversations

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

It discloses the 20-result limit and the presence of hasPrevious/hasNext pagination flags, which is useful behavioral information beyond the name. However, with no annotations provided, the description carries the full burden and still does not mention ordering, read-only behavior, authentication needs, or what fields each conversation contains.

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 sentence that front-loads the key behavior (first 20 conversations) and immediately notes the pagination flags. Every word earns its place with no redundancy.

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 zero-parameter listing tool, it covers the most important runtime facts: result cap and pagination existence. But because there is no output schema, the description leaves out conversation field details, ordering, and whether a valid session is required, which are relevant for an agent invoking this tool correctly.

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 input schema is empty, so parameter documentation is trivially complete. The description adds the only relevant call detail: that the endpoint returns at most 20 conversations and pagination flags.

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 states that the tool lists the first 20 conversations and references the /conversations/list endpoint, which gives a specific resource and scope. However, it does not explicitly differentiate this tool from sibling list_pending, 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 description gives no guidance on when to use this tool instead of alternatives such as list_pending or get_conversation. There is also no mention of prerequisites like having an active session, which siblings like open_login and check_session suggest may be relevant.

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