slack_list_channels

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

With no annotations provided, the description must carry the behavioral burden, but it only states the high-level action and filtering options. It does not disclose pagination behavior, the meaning of the default limit, whether archived channels are included, or what the return structure looks like. The read-only nature is implied but never explicitly stated.

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 short and front-loaded with the primary action and resource. The second sentence efficiently summarizes the filtering and search capabilities. No redundant wording is present.

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?

The description and schema together cover the basic input contract, but there is no output schema and the description does not explain return format, default behavior when workspace is omitted, or how results are ordered/paginated. For a simple list tool, this is adequate but leaves some gaps.

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 the schema already documents all four parameters with defaults and descriptions. The description adds only a generic mention of type filtering and name search, which partially mirrors the type and query parameters but does not add meaningful detail beyond the schema.

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 identifies a specific action ('List') on a specific resource ('Slack channels, DMs, and group chats') and notes the filtering/search capabilities. It is clear enough to distinguish from siblings like slack_send_message and slack_read_messages, though it does not explicitly name any sibling alternatives.

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 implies the tool is for listing and filtering channels but gives no explicit guidance on when to use it versus slack_search, slack_list_users, or slack_list_workspaces. No exclusions or alternative recommendations are provided.

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