list_chats

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

With no annotations, the description carries the full burden. It discloses the ordering guarantee and the host-side rendering behavior (inline card, don't repeat contents), which is genuinely useful context, but it never states read-only semantics, page-size limits, or what happens when limit exceeds the total conversation count.

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?

Purpose and ordering are front-loaded in the first sentence, followed by the host-rendering note and compact parameter list. The Claude-specific rendering paragraph is somewhat verbose but earns its place by preventing duplicated output.

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?

An output schema exists, so return values need not be explained. For a zero-annotation list tool the description covers purpose, ordering, paging, and host display adequately; the only real gap is not routing the agent away from sibling retrieval/search tools.

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 0%, so the description must document the parameters and it does: limit as maximum conversations to return with default 30, and offset as conversations to skip for paging. It adds meaning for offset beyond the bare schema, though it adds little beyond the schema's own default for limit.

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 conversations') plus the sort order ('most recently active first'), which the agent cannot infer elsewhere. It does not, however, name or distinguish itself from the closest siblings (get_chat_messages, search_messages), so differentiation is left to inference.

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?

Usage is implied by 'List conversations' — browsing rather than reading or searching a specific conversation. There is no explicit statement of when to prefer this over search_messages or get_chat_messages, and no prerequisites or exclusions are given.

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