list_channels

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

With no annotations provided, the description bears the full responsibility for behavioral disclosure. It only states the action without detailing what is returned (e.g., channel types, names, IDs), whether permissions are needed, or any pagination/limits. The simple read nature is clear, but the description fails to disclose potential nuances like whether private channels or categories are included.

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, concise sentence that directly states the tool's purpose without any fluff. It is front-loaded with the verb and resource, making it immediately understandable. Every word earns its place.

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?

This is a simple tool with one parameter and no output schema. The description is adequate for a basic list operation, but it does not specify what the returned list contains (e.g., channel names, types, IDs). Given the lack of output schema, a bit more detail would improve completeness, but the tool's simplicity keeps the gap modest.

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 input schema fully covers the parameter 'guild_id' with a description 'Server ID', so the schema provides the necessary semantics. The tool description does not add anything about parameters; however, given 100% schema coverage, a baseline of 3 is appropriate.

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's function: 'List all channels in a Discord server.' The verb 'list' is specific, and the resource 'channels' with scope 'in a Discord server' distinguishes it from sibling tools like get_channel_info, which retrieves a single channel. The word 'all' reinforces the full listing intent.

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 provides no guidance on when to use this tool versus alternatives such as get_channel_info or get_guild_info. It does not mention any exclusions, prerequisites, or scenarios where another tool would be more appropriate. The usage context is entirely implied.

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