discord_get_forum_channels

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that it 'Lists all forum channels,' which implies a read-only operation, but doesn't cover critical aspects like authentication requirements, rate limits, pagination, error handling, or the format of the returned data. This leaves significant gaps in understanding how the tool behaves in practice.

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, efficient sentence that front-loads the key information ('Lists all forum channels') without any unnecessary words. It directly communicates the tool's function and scope, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what the output looks like (e.g., list format, channel details), authentication needs, or potential errors. For a tool that interacts with an external API like Discord, this leaves too many unknowns for reliable agent invocation.

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 specifies that it lists forum channels 'in a specified Discord server (guild),' which adds context to the 'guildId' parameter by clarifying its purpose. However, with 0% schema description coverage and only one parameter, this provides minimal additional value beyond what the parameter name implies. The baseline is appropriate given the low parameter count.

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 action ('Lists') and resource ('all forum channels in a specified Discord server'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'discord_get_server_info' or 'discord_get_forum_post', but the focus on forum channels is specific enough to avoid confusion with most siblings.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this is the primary way to retrieve forum channels compared to other methods or tools, nor does it specify prerequisites like needing the guildId. The description only states what it does, not when it should be used.

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