Discord MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool's capabilities (date range, keyword search, pagination), it doesn't describe important behavioral aspects like rate limits, authentication requirements, error conditions, or what the response format looks like. For a read operation with multiple parameters, this leaves significant gaps in understanding how the tool behaves.

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 - a single sentence that efficiently communicates the core capabilities. Every word earns its place, and it's front-loaded with the most important information about what makes this tool 'advanced'.

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 complex tool with 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain return values, error handling, or important behavioral constraints. While the schema covers parameter documentation well, the description fails to provide the contextual understanding needed for effective tool selection and use.

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 description mentions 'date range, keyword search, and pagination' which maps to some parameters (start_date, end_date, keyword, before/after). However, with 100% schema description coverage, the schema already documents all 9 parameters thoroughly. The description adds minimal value beyond what's already in the structured schema, meeting the baseline expectation.

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's purpose as 'Advanced message retrieval with date range, keyword search, and pagination', which specifies the verb (retrieval) and resource (messages) along with key capabilities. However, it doesn't explicitly differentiate from its sibling 'discord_get_messages', leaving some ambiguity about what makes this 'advanced' version distinct.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of when to choose this over the simpler 'discord_get_messages' sibling, nor any context about prerequisites or typical use cases for these advanced filtering capabilities.

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