list_chats

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety profile is provided. The description adds the cap on limit (200), offering one behavioral constraint, but does not elaborate on ordering or pagination. Barring annotations, this is sufficient but minimal.

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?

Two sentences convey purpose, return details, usage hint, and a limit constraint with no wasted words. The information is front-loaded and efficiently delivered.

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?

The tool is simple (one optional param, read-only) and an output schema exists, so the description doesn't need to detail return formatting. It covers the key workflow (list chats -> get messages) and limit cap, making it sufficiently complete for the low 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?

The schema provides only the integer type and default for limit, with 0% coverage. The description compensates by noting the cap at 200, giving practical meaning beyond the schema. However, it doesn't explain the exact effect of varying limit, but this is largely evident.

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 'List the most recently active conversations' with a specific verb and resource. It also specifies return content (identifier, display name, last message time), distinguishing it from sibling message-retrieval tools.

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 mentions using the returned identifiers with get_messages or send_to_chat, which provides follow-up usage context. However, it does not explicitly state when to use this tool versus alternatives like get_recent_messages, and omits any exclusions.

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