fetch_messages

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

With no annotations, the description provides useful behavioral detail: messages are returned oldest first, and full search is not available. However, it omits the return format, default limit, and any rate-limit or error behavior, leaving gaps for an agent.

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: first states the core action with ordering, second adds a relevant API limitation. No filler, front-loaded with the most important information.

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 tool has no output schema and no annotations, so the description should clarify the return value, default limit, and parameter semantics. It does not, leaving significant operational gaps for correct 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?

Schema description coverage is 0% and the description does not explain the 'limit' or 'channel' parameters. The phrase 'Discord channel history' hints at the channel, but 'limit' is entirely unexplained, failing to compensate for the missing schema 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 a specific action ('Fetch'), resource ('Discord channel history'), and gives ordering ('oldest first') and scope ('recent'). It distinguishes this read tool from sibling write tools like send_message, reply, and edit_message.

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 intended use is implied ('Fetch recent Discord channel history') and the API limitation offers some context, but there is no explicit guidance about when to choose this over siblings or when not to use it. No alternatives are directly named.

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