List Discord channels

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds meaningful behavioral context beyond annotations by noting that the guild must be allowlisted and that optional channel allowlisting may filter results. This is valuable and not contradictory.

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 two concise sentences, front-loaded with the action 'Lists channels'. It contains no redundant phrasing or unnecessary detail, earning its place efficiently.

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 tool with one parameter, strong annotations, and no output schema, the description provides sufficient context. It states the guild scope and allowlisting behavior, though it could be slightly clearer about what 'allowlisting' entails or potential error cases, but this is not a significant 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. While it mentions 'one allowlisted Discord guild', it does not explicitly describe the 'guildId' parameter or its format, leaving the connection implied. The single parameter name is self-explanatory, but the description adds no direct semantic clarification.

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 tool lists channels in a specific Discord guild, using a specific verb (lists) and resource (channels). It distinguishes itself from siblings like discord_list_guilds (lists guilds) and discord_get_channel (gets one channel) by specifying the scope of one allowlisted guild.

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 usage context is implied by the description: it is for listing channels within a particular guild. However, it does not explicitly mention when to use this tool over alternatives or provide exclusion criteria, such as 'use discord_get_channel for a single channel'.

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