discord_archive_forum_stream

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It notes that the tool 'streams' threads and includes active/archived threads with time filtering, but does not clarify whether 'archives' means a read-only export or a state-changing action (e.g., marking threads archived), nor does it mention permissions, rate limits, or side effects. This ambiguity is a significant gap.

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, information-dense sentence that front-loads the primary action ('Archives') and efficiently includes key scope and filtering capabilities without unnecessary words.

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 explain what the archive operation returns (e.g., a file, a confirmation, a link) and any prerequisites (e.g., required permissions). It does neither, leaving the agent uncertain about expected outputs and preconditions.

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 descriptions cover 100% of the parameters, so the baseline is 3. The description adds a bit of context by mentioning 'time range filtering' and 'active and archived threads', which maps to afterDate/beforeDate and includeArchived, but it does not add substantive syntax or format details beyond the schema.

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 uses a specific verb ('Archives') and identifies the exact resource ('entire forum channel') and mechanism ('streaming all threads and their messages'). It also clarifies scope (active/archived threads, time range filtering), which differentiates it from siblings like discord_archive_multiple_forums.

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 a clear use case—archiving a single entire forum channel with optional time filtering—but does not explicitly state when to use it versus alternatives such as discord_archive_multiple_forums or discord_get_forum_post_stream. There are no exclusions or when-not-to-use notes, giving only implied guidance.

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