List Discord messages

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description adds meaningful constraints: 'bounded page' (pagination limit), 'allowlisted guild channel' (access restriction), and the requirement of Message Content Intent (prerequisite). These are useful operational details not captured by 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?

Two concise sentences: the first clearly states the core function and scope, the second adds a crucial prerequisite. No redundant information, perfectly front-loaded.

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?

The description covers the primary purpose and a key restriction, but since there is no output schema, it does not explain the return format or pagination behavior (e.g., how to request the next page). Given the tool's four parameters and complexity, this is a noticeable gap, though the description is adequate for basic usage.

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?

The schema has zero description coverage, and the description does not explain the `after` and `before` parameters or their relationship. It only mentions 'bounded page,' which hints at `limit` but leaves `after`/`before` semantics ambiguous. Relies heavily on parameter names, which may not be self-explanatory for pagination.

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 reads a bounded page of messages from a specific channel, using the specific verb 'reads' and resource 'messages.' It also distinguishes from siblings by mentioning 'messages' rather than guilds/channels and 'bounded page' implying a list operation.

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?

Provides clear context: it targets one allowlisted guild channel and requires Message Content Intent. This indicates when to use it (for reading messages from a specific channel) and implies the need for allowlisting, but does not explicitly name alternative tools for single-message retrieval.

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