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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful scope constraint that only channels visible to the app's bot are returned, but says nothing about ordering, pagination, or what fields come back.

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 purpose, which is good. But the second sentence spends its entire budget on a parameter the tool does not accept, so it does not earn 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?

For a simple two-parameter read tool with a 100% documented schema and safe annotations, most of what an agent needs is present. Missing: confirmation that results are read-only server-scoped data with no pagination, and there is no output schema to explain the returned channel objects.

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 app_id and server_id are already fully documented. However, the description explains a "type" parameter (0 for text, 4 for categories) that does not exist in the input schema, which can mislead an agent into passing an unsupported argument.

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 ("Lists the channels of a Discord server") and scopes it to servers the app's bot is in, which distinguishes it from siblings like list_roles and list_servers. It does not explicitly contrast itself with any alternative, but the resource is unambiguous.

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?

There is no guidance on when to use this versus alternatives such as discord_api_request or list_servers, and no stated prerequisites (e.g., the bot needing the right intents/permissions to see channels). The only implied condition is that the bot must be in the server, which is stated as scope rather than usage advice.

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