discord_get_forum_channels

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

No annotations are provided, so the description carries the full burden. It states the action is a list operation, implying read-only behavior, but does not disclose any behavioral traits like permissions required, rate limits, pagination, or output format. This leaves significant gaps for a tool with no annotation coverage.

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 core purpose ('Lists all forum channels') and includes necessary context ('in a specified Discord server (guild)'). There is no wasted wording, making it highly concise and well-structured.

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 simplicity (1 parameter, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it lacks details on behavioral aspects like permissions or output structure, which are important for effective use, making it incomplete for a tool with no supporting structured data.

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?

With 0% schema description coverage and 1 parameter, the description adds essential meaning by clarifying that the 'guildId' parameter specifies the Discord server from which to list forum channels. This compensates for the lack of schema details, though it could further explain the format or sourcing of guildId.

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 specific action ('Lists') and resource ('all forum channels in a specified Discord server'), distinguishing it from siblings like discord_get_forum_post (which retrieves a single post) and discord_get_server_info (which provides general server information). It precisely defines scope without ambiguity.

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 by specifying 'in a specified Discord server (guild)', which provides context for when to use it (to retrieve forum channels from a server). However, it lacks explicit guidance on when not to use it or alternatives, such as not using it for non-forum channels or suggesting discord_get_server_info for broader server details.

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