discord_get_messages

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

The description discloses the read-only nature ('Read messages') and mentions paging behavior, which is helpful. However, with no annotations, it fails to communicate potential constraints like rate limits, permission requirements, or that limits are capped at 100. The description is adequate but not comprehensive.

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 extremely concise at two sentences, front-loading the core purpose and then adding critical paging guidance. Every word contributes meaning with no redundancy or fluff.

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?

While the description covers the main use case and paging, it lacks details about return format (e.g., message order, fields included) and does not explain what happens if no messages are found or when the limit is exceeded. For a tool with 5 parameters and no output schema, more context would be beneficial, but the description is still functional.

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 baseline is 3. The description adds value by explaining the semantic purpose of before/after/around parameters for paging history, which goes beyond the schema descriptions that merely state 'Get messages after this message ID'. This guidance helps an AI agent understand how to use these parameters together.

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 action 'Read messages from a channel', specifying the resource (channel) and verb (read). It distinguishes itself from siblings like discord_get_message (single message), discord_send_message, and discord_search_messages by focusing on retrieving multiple messages with paging support.

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 advises using 'before/after/around (message IDs) to page through history beyond the latest 100', providing clear context for when to apply these parameters. It implies basic usage without paging (just channelId and limit) but does not explicitly state when not to use this tool or mention alternatives like discord_search_messages.

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