discord_get_forum_channels

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

The 'read-only' claim merely restates readOnlyHint=true. It does add the shape of returned items (id, name, topic, parent category), but with annotations already covering the safety profile and an output schema present, there is no extra context on scope, pagination, or limits.

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?

Two sentences, no filler: the scoping and returned fields are front-loaded, followed by the sibling routing. Every clause carries information.

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?

With annotations covering safety, a fully documented single parameter, and an output schema handling return values, the description is nearly complete. It could note volume/pagination expectations for a server-wide list, which is the only remaining 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?

Only one parameter, guild_id, and the schema documents it at 100% coverage including the snowflake pattern. The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('List the forum channels in a server') and enumerates the returned fields, which lets an agent distinguish this from discord_list_channels and the forum-sibling tools without opening any schema.

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?

Explicitly routes to alternatives for adjacent tasks: discord_get_forum_tags for a forum's tags and discord_list_forum_threads for its posts. It does not address how this differs from the broader discord_list_channels, so the sibling separation is clear but not exhaustive.

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