read_discord_messages

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

With no annotations provided, the description carries the full burden. It declares the tool is 'read-only', which is good, but does not disclose other behaviors like authentication requirements (bot presence in channel), rate limits, or error handling. Some behavioral context is added, but not exhaustive.

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?

Extremely concise and front-loaded: two sentences. The first clearly states the purpose and the second provides usage context. Every sentence adds value with no redundancy.

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?

Given 8 optional parameters, no output schema, and no annotations, the description is adequate for the core purpose but lacks details about return format (e.g., what fields are in messages) and edge cases (e.g., channel not found or no messages). The schema covers parameters but output is not described.

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 100%, so the baseline is 3. The description does not add significant meaning beyond what the schema already explains for each parameter. It mentions channel_id as primary but the schema already covers all parameters with descriptions.

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 recent messages from a specific Discord channel by channel ID.' It uses a specific verb and resource, and distinguishes from sibling tools like send_discord_message or reply_discord_message by emphasizing it is a read-only action.

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?

Explicitly tells when to use: 'Use this when the user asks what is happening in a Discord channel or wants context from recent Discord messages.' It implies not for sending or replying by stating 'read-only action', but does not specify when not to use or alternatives in detail.

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