Read messages

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

Annotations already provide readOnlyHint=true, indicating safe read operation. The description adds behavioral details: returns digest, oldest first, and includes resolved reply references. No contradictions with annotations.

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 two sentences with no wasted words. It front-loads the purpose and key fields, then adds pagination guidance. Highly concise and well-structured.

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?

No output schema exists, but the description adequately explains the return content. Given the tool's simplicity and the presence of sibling tools like 'search_messages' and 'get_message', the context is largely complete. Minor gap: no mention of rate limits or default behavior for missing guild.

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 description does not need to reiterate parameter details. It adds context for the 'before' parameter by mentioning 'next_before' cursor pattern, but this is implied rather than explicit. Adequate given high schema coverage.

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 it reads recent messages from a channel, lists included fields (author, time, content, attachments, reactions, resolved reply references), and mentions ordering (oldest first). This distinguishes it from sibling tools like 'get_message' (single message) and 'search_messages' (search).

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 mentions pagination ('Use next_before to page further back'), providing usage context. However, it does not explicitly state when not to use this tool or mention alternatives like 'search_messages' for filtering.

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