chat_list

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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description adds the fixed conversation scope and the oldest-first ordering, which are useful traits, but says nothing about page size behavior or what happens when the cursor is omitted.

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?

One sentence, front-loaded with the verb and scope, with the cursor caveat trailing. Nothing is redundant, though the quoted conversation name plus ordering plus cursor in a single clause is slightly dense.

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?

An output schema exists, so return values need no explanation, and the tool is a simple three-optional-parameter read. The description covers scope, ordering and one cursor, leaving only forward pagination and default sizing to the schema.

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 100%, so limit, after_id and before_id are already documented with semantics and mutual exclusivity. The description only echoes before_id as a cursor and adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 names a specific verb (List) and resource (messages) scoped to a single conversation, '我的设备', and states ordering (oldest first). That distinguishes it from the write-side sibling chat_send, though it never names that sibling outright.

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?

It mentions the optional before_id cursor, which implies paginated backward traversal, but gives no explicit when-to-use or when-not guidance and does not explain the after_id alternative for forward paging that the schema exposes.

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