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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: hasMore signals direction of remaining messages, an empty page is the valid result for a task chat with no messages, and attachments carry an attachToken that can be reused in a spec/result.

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 paragraph, front-loaded with the core behavior and direction semantics, with no filler sentences. It is slightly run-on, packing pagination, empty-page, and attachToken facts into one block, but 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, the description usefully previews return semantics (hasMore, empty page, attachToken) for a cursor-paginated read tool. Given the read-only annotations and full schema coverage, an agent has everything needed to call it correctly; only the exact response shape is unspecified.

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 baseline is 3; the description nonetheless adds meaning by explaining that cursors come from a previous response and encode direction (after = newer, before = older). The limit and chatID parameters are left entirely to the schema, so it does not fully compensate beyond the baseline.

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 states a specific verb and resource ('Returns chat messages') and defines the scope precisely via cursor semantics (oldest-to-newest with a cursor, latest without). It is clearly distinguishable from the mutation siblings (chat_send, chat_message_delete, chat_message_update) by its read behavior, 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?

It gives concrete conditions for each mode: no cursor returns the latest messages, an after cursor returns newer messages (e.g. replies to a sent one), and a before cursor returns older messages. That is clear usage context for pagination, but it offers no when-not-to-use or sibling routing guidance.

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