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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: authentication requirement, authorization scope (only conversations the caller participates in), default ordering, and that the 'after' mode supports polling. No contradictions.

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 dense, front-loaded sentence with the auth prerequisite and scope first, then paging semantics. Nearly every clause earns its place, though the 'nextBefore' naming slip costs a little clarity.

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?

For a read-only listing tool with full schema coverage and complete annotations, the description supplies the remaining needed context: auth, scope restriction, ordering and paging/polling modes. No output schema exists, so return-format gaps are not a deficiency.

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 the schema already documents all four parameters, establishing a baseline of 3. The description reinforces ordering semantics (default descending, after=ascending), but it names a parameter 'nextBefore' that does not exist in the schema (the parameter is 'before'), which slightly muddies rather than clarifies.

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+resource (read messages in a conversation) and adds scope ('仅本人参与会话'), which is more than the name conveys. It implicitly distinguishes itself from siblings like send_message, get_conversation and list_my_conversations, though it never names an alternative explicitly.

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?

Gives concrete usage context: login required, default reverse-chronological order, 'before' for paging backward and 'after' for incremental forward polling. That covers the main call patterns, but there is no explicit when-not-to-use or named sibling alternative.

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