List Slack Channels

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

Discloses that it lists channels the bot is a member of or pre-defined channels, and mentions pagination. However, no annotations exist, and the description does not state side effects, required permissions, or rate limits. As a read operation, it should explicitly note it does not modify state.

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?

Single sentence, no redundancy, efficiently packs core information: what is listed and pagination support. Front-loaded with verb and resource.

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 list tool with 2 parameters and no output schema, the description covers key scope and pagination. Missing details about return fields, but this is not critical given the tool's straightforward nature.

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% with clear descriptions for limit and cursor. The description adds 'pre-defined channels' context but does not enhance understanding of parameters beyond what the schema already provides. 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?

Clearly states it lists public and private channels with pagination, specifying scope (bot member or pre-defined). Does not explicitly differentiate from siblings but the verb 'list' and resource 'channels' are distinct from other tools like posting messages or getting history.

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?

No guidance on when to use this tool versus alternatives. For example, if an agent needs to find a channel by name or get all channels in workspace, this description does not clarify limitations or suggest other tools.

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