list-chat-messages

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

Without annotations, the description provides some behavioral info: it lists returned fields and notes that contentMode:none is cheap. However, it does not disclose ordering (which is in schema but not in description) or scope (all messages or only current user's). No side effects or read-only indication.

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?

The description is only two sentences, immediately stating the tool's purpose and then providing use cases and a tip. No filler words.

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?

Given the low complexity (3 parameters, no output schema), the description covers purpose, use cases, fields returned, and a performance tip. Missing details like ordering and scope, but overall adequate.

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% with each parameter already described. The description adds minimal value beyond the schema, only repeating the cheapness tip for contentMode:none. Baseline 3 is 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 clearly states the tool lists recent chat messages with specific fields (id, author, time, whisper/blind, content preview), and it provides explicit use cases (find ids for delete, verify a post, preview before export) that help differentiate it from siblings like delete-chat-messages and export-chat-log.

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 explicitly states when to use the tool (to find ids for delete, verify, preview) and provides a usage tip (contentMode:none for cheap operation). However, it does not mention when not to use it or mention alternatives like export-chat-log for full export.

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