discord_get_forum_channels

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

With no annotations, the description carries the full burden. It accurately conveys the read-only nature ('Lists') and the scope, but it does not disclose return format, authentication requirements, or potential errors. The description is adequate but lacks extra behavioral context.

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 fluff. It immediately states the action and object, 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?

The tool is simple with one parameter, and the description covers purpose and scope well. However, with no output schema or annotations, it does not describe return values or any prerequisites (e.g., login), leaving a small but notable 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?

The input schema has 0% description coverage, but the description compensates by clarifying that 'guildId' refers to 'a specified Discord server (guild)'. This adds meaning beyond the parameter name and helps agents understand the expected value, though it doesn't specify format or how to obtain the ID.

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 specific action ('Lists') on a clear resource ('forum channels') with a defined scope ('in a specified Discord server (guild)'). This clearly distinguishes it from sibling tools like discord_get_forum_post (which retrieves a single post) and discord_list_servers (which lists servers, not channels).

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 clear context for when to use the tool: whenever all forum channels in a guild are needed. However, it does not explicitly mention exclusions or alternatives (e.g., use discord_get_forum_post for a specific post), but the context is unambiguous enough for an agent to select appropriately.

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