discord_read_messages_stream

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

With no annotations, the description carries the full burden. It discloses that the tool returns all message events including progress updates and specifies a default time range, adding behavioral context. However, it omits details like authentication requirements, stream termination behavior, or error handling, which would improve transparency 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?

The description is two concise sentences with no redundant wording. The primary action is front-loaded, followed by key details about time range and return data, making it efficient and easy to parse.

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 the tool's streaming nature and lack of output schema, the description provides essential return information ('all message events including progress updates') and a default time frame. It could be more complete by explaining stream lifecycle, pagination, or rate limits, but for a relatively simple tool, it covers the core usage context adequately.

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 input schema already provides clear descriptions for all three parameters (100% coverage), so the baseline is 3. The description adds value by explaining the default behavior (last 10 days) and implying the purpose of time range filtering, which goes slightly beyond the schema's basic 'only fetch after/before this date' text.

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 streams messages from a Discord channel, uses a specific verb ('streams') and resource ('Discord channel'), and adds distinctive details like time range filtering and default last 10 days. It differentiates from sibling tools like discord_read_messages by emphasizing streaming and progress updates.

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 usage through the term 'streams' but does not explicitly compare with alternatives like discord_read_messages or discord_search_messages. No exclusionary or conditional guidance is provided, making the 'when to use' context somewhat inferred rather than explicit.

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