list_chat_messages

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

No annotations are present, so the description bears full responsibility. It only states 'list recent messages' without revealing read-only nature, pagination behavior, rate limits, or error handling. For a read operation, minimal behavioral context makes it harder for an agent to anticipate results.

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 a single sentence with no wasted words. It is front-loaded and efficient. However, it is slightly too terse; a bit more context (e.g., 'ordered by recency') would improve clarity without sacrificing conciseness.

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 simple tool with 2 parameters and no output schema, the description is minimally adequate. It covers the basic action but omits details like default ordering, response structure, and pagination. Given the tool's low complexity, a score of 3 is appropriate.

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 adds no extra meaning beyond the schema definitions. Both parameters are already well-described in the schema, so the description does not improve understanding of their semantics.

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 'List recent messages in a chat' clearly specifies the action (list) and resource (messages in a chat). It differentiates this tool from siblings like 'list_channel_messages' and 'list_chat_members' by focusing on messages versus members or channels. However, it does not specify ordering or time range, so it is not a perfect 5.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list_channel_messages' or search tools. There's no mention of prerequisites (e.g., chat existence) or exclusions. This is a significant gap given the large number of sibling list tools.

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