discord_get_recent_messages

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

No annotations are provided, so the description carries full burden. It only states the basic action 'fetch recent messages' and does not disclose ordering, pagination, default limit, rate limits, or side effects. It implies a read operation but offers no additional behavioral details.

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, front-loaded sentence with no wasted words. It clearly states the purpose at the start and omits unnecessary detail. It is appropriately concise.

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?

Although an output schema exists, the description is incomplete for a tool with three parameters. It does not clarify the optional 'limit' and 'guild_id', nor does it set expectations about message ordering or count. For a read-heavy Discord tool, this is a significant gap.

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 0%. The description does not explain the meaning of 'limit' or 'guild_id', and only indirectly references 'channel' via 'from a channel'. It fails to compensate for the absence of schema parameter descriptions, leaving the agent without guidance on how to set optional fields.

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 states a clear verb and resource: 'Fetch recent messages' from a channel. It is specific enough to distinguish from siblings like discord_get_message (singular) and discord_list_channels (lists channels, not messages). The scope is unambiguous.

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. It does not mention when to prefer discord_get_message (for a single message) or discord_list_channels (to enumerate channels). There is no exclusion condition or recommended context.

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