discord_read_messages

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds context about 'allowed channel', implying permission restrictions, but does not discuss pagination, rate limits, or the structure of the returned messages.

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 redundant words, effectively front-loading the primary action. It is appropriately sized for the tool's simplicity.

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 read tool with readOnlyHint and openWorldHint annotations, the description is mostly sufficient. However, it lacks detail on return value structure (e.g., message content, metadata) and the exact meaning of 'allowed' is vague.

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 description coverage is only 50%; channelId has a description, but limit lacks one. The tool description does not explain parameter behavior, particularly how limit controls the number of messages returned. The schema's default/min/max provide constraints but not semantic meaning.

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 recent messages from a channel, using a specific verb and resource. It distinguishes from sibling tools like discord_send_message and discord_admin_messages by focusing on read-only access to messages from an allowed channel.

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 implies the tool is for reading message history but does not explicitly state when to use it over alternatives like discord_admin_messages or discord_list_channels. No exclusions or alternative recommendations are provided, leaving usage somewhat implied.

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