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

The description adds a real auth requirement (chat:read scope), which is exactly the kind of behavioral detail annotations do not carry. However, it says nothing about ordering, pagination, or result set limits, and the readOnlyHint=false annotation sits in mild tension with a pure 'List' operation the description never reconciles.

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, no filler, and the core action is front-loaded ahead of the prerequisite. Every clause earns its place.

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 parameters, the description is the only source of information about the result, yet it never characterizes the return (pagination, ordering, whether conversations are empty-safe). Adequate but leaving a clear gap for a list endpoint.

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 tool takes no parameters, so the schema carries nothing an agent must interpret; the baseline for a zero-parameter tool applies. The description correctly does not clutter itself with parameter talk.

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 (List) and resource (the human's conversations), which is enough for an agent to know what it returns at a glance. It does not, however, differentiate itself from the sibling read_messages, which an agent could plausibly confuse with listing conversations.

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 only guidance is a prerequisite (chat:read scope), not a usage rule. Nothing says when to prefer this over read_messages or how it relates to the other conversation-adjacent sibling tools.

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