discord_list_channels

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered structurally. The description usefully adds that categories, voice and forums are all included and that omission of guild_id broadens scope to all guilds, but says nothing about pagination, result limits, or required bot permissions.

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 short sentences, front-loaded with the core action and immediately followed by the one behavioral caveat. Nothing is redundant or padded.

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?

For a simple read-only list tool with no output schema and a single fully documented parameter, the description covers what is needed to invoke it correctly. The only gap is the shape of the returned channel list (fields, ordering), which is minor for this tool type.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning the schema cannot: the parameter is optional and omitting it changes the query from one guild to all guilds. That is real semantic value beyond the schema's bare 'Server (guild) 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 verb and resource ('List channels') and adds scope detail ('all types, including categories, voice and forums'). It implicitly separates itself from discord_list_guilds via the 'every server the bot is in' note, though it never names a sibling explicitly.

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?

It gives one concrete usage rule ('Omit guild_id to list every server the bot is in'), which is genuine conditional guidance. However, it names no alternatives (e.g. discord_get_channel for a single channel, discord_list_guilds for servers), so the agent must infer when this tool is preferable.

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