listSlackChannels

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

Without annotations, the description uses 'Retrieves' to signal a read-only operation and notes the authentication requirement. It does not disclose details about return fields, pagination, or access limits, which are relevant for a list operation.

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, front-loaded sentence with no redundant words. It efficiently conveys the operation, resource, and scope.

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?

Given the tool's simplicity (no params, no output schema), the description adequately covers its purpose and scope. It could explicitly mention return fields (e.g., channel names and IDs), but it's sufficiently complete for a straightforward list operation.

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 is empty (zero parameters), so no parameter information is needed. The description's mention of 'public and private channels' clarifies the output scope but not parameters; the baseline of 4 for zero-param tools applies.

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 action ('Retrieves a list'), the resource ('public and private channels'), and the scope ('authenticated user's Slack workspace'). It distinguishes itself from siblings like readSlackChannel (which fetches a single channel) and postSlackMessage (which sends messages).

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 its use case (listing all channels the user can access) but provides no explicit guidance on when to prefer this over readSlackChannel or other list tools. Sibling context shows alternatives, but the description itself doesn't mention them, so usage is only implied.

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