list_chats

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat safety. It adds the 'newest first' ordering behavior, which is not in the schema. It also clarifies the mapping between chats and tickets, which is useful. However, it doesn't mention pagination specifics beyond what the schema provides.

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 sentence with no waste. It front-loads the core action and adds a clarifying parenthetical about the tickets relationship, which is efficient.

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?

Given the tool is simple (list, no required params, no output schema), the description is sufficient. It explains the output (tickets) and ordering. The only minor gap is whether it includes all chats or if there are scope limitations, but annotations (openWorldHint) suggest broad scope. Overall complete for its complexity.

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 100%, so the parameters are well-documented. The description adds that results are ordered 'newest first', which is relevant for page/per_page usage, but it doesn't add substantial semantics beyond the schema.

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 the tool lists chat conversations, and clarifies the relationship to Zendesk tickets. It distinguishes this from list_tickets by noting these are specifically chat/messaging conversations, though it doesn't explicitly name sibling alternatives.

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 implies when to use this tool (when you need chat conversations) but does not explicitly state when not to use it or recommend alternatives. It doesn't contrast with list_tickets or search, so an agent might not know to use search for more complex queries.

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