runrunit_discord_list_channels

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

The description discloses one meaningful behavior: the target guild is obtained from DISCORD_GUILD_ID or resolved from DISCORD_CHANNEL_ID. However, with no annotations present, the full burden falls on the description, and it does not mention that the operation is read-only, what the response contains, or failure behavior when env vars are missing.

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 short sentences with the main purpose first and the targeting detail second. There is no filler, and every sentence contributes useful 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?

For a simple one-parameter tool with no output schema, this description is usable but slightly incomplete. It does not describe the returned channel data, such as whether channel IDs, names, or both are returned, which an agent may need when passing results to send_message or get_or_create_channel. With no annotations, there is also no safety context beyond the word 'list'.

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 schema already documents guild_id as 'optional if env set', but the description adds extra value by explaining that DISCORD_CHANNEL_ID can be used to resolve the guild. This helps the agent decide whether to supply guild_id or rely on environment configuration.

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 uses a specific verb ('List') and a clear resource ('channels in the Discord server'), making the tool's purpose immediately obvious. It is also clearly distinct from sibling Discord tools like send_message, create_channel, and get_or_create_channel.

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 clearly frames when this tool is relevant: when channel enumeration from the configured Discord server is needed. It does not explicitly contrast with discord_get_or_create_channel or discord_send_message, but the read-only list intent is unambiguous enough for an agent to select it correctly.

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