list_chats

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies a read-only listing and states the ordering, but it does not disclose the return shape, whether group chats or newsletters are included, pagination behavior, or any authentication or availability caveats.

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 short sentence with no filler. The action is front-loaded and the most important qualifier, sorting by recent activity, is included without unnecessary detail.

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 output schema and no annotations, the description should do more to clarify what a 'chat' is, what fields are returned, and how this differs from other list tools. The provided text is minimally adequate for a simple call but leaves key context to inference.

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 fully documents the single optional 'limit' parameter with default, minimum, and maximum, so the practical gap is small. However, with 0% schema description coverage, the description adds no meaning about parameters and does not compensate for its absence.

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 uses a clear verb ('List'), a specific resource ('chats'), and adds a useful qualifier ('sorted by recent activity'). It is distinguishable from sibling tools like list_messages and list_status by resource name, though it does not explicitly define what counts as a chat or differentiate itself from list_groups.

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 use this tool versus list_groups, list_messages, list_newsletters, or search_messages. The description states only what the tool does, not the conditions under which it should be selected.

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