chats_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without description help. The description adds only transport plumbing (POST path, gRPC method, socket event), which is not behavioral context a caller needs. It says nothing about ordering, default page size, or what happens past the last page.

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?

A single short line with no filler, and the resource statement comes first. The parenthetical transport dump is arguably noise for a caller, and the mid-string line break is awkward, but it is efficient overall.

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, no parameter documentation, and 0% schema description coverage, the description should carry more weight. It omits the return shape, pagination semantics, and defaults, leaving an agent unable to call this confidently beyond passing a channelId.

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% and the description never mentions page, limit, or channelId. The word 'page' faintly implies pagination, but the agent gets no default limit, no maximum, and no indication that channelId is the mandatory identifier versus an optional scope. The description fails to compensate for the coverage 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 fragment 'A page of a channel's chats' names the resource and implies listing, but supplies no verb and does not distinguish this tool from close siblings such as chats_search, chats_sync, or chats_get. It also does not clarify how it differs from channels_list, which lists a different entity. An agent can infer the gist but must guess at the exact scope.

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 when-to-use guidance at all: no statement about choosing this over chats_search (filtered lookup) or chats_sync (delta sync). No prerequisites or context are given. The description is purely informational about the resource.

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