clickup_chat_channel_list

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

No annotations are present, so the description must fully explain behavior. It notes pagination and that the tool lists channels the user can see (implying authorization). However, it does not disclose details like rate limits, required permissions beyond authentication, or how pagination works (e.g., page size, cursor usage). The description adds some value but leaves gaps.

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 two sentences, each serving a clear purpose: stating the operation and providing pagination details, return fields, and an alternative tool. No redundant information, front-loaded with primary purpose.

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 list tool with no output schema, the description covers the return fields (id, name, visibility, topic, last_message_at) and mentions pagination. It also references a sibling for creation. It does not mention other relevant siblings like get or delete, but the core information is sufficient for an agent to invoke correctly.

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 has 100% description coverage (both parameters have meaningful descriptions). The tool description does not add new parameter information beyond the schema; it only lists return fields. The schema already explains the parameters well, so the description adds minimal value. Baseline 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 explicitly states 'List all ClickUp Chat channels in a workspace that the authenticated user can see.' It uses a specific verb (list) and resource (chat channels), and distinguishes from siblings like clickup_chat_channel_create (create) and clickup_chat_channel_get (single channel).

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 mentions 'Uses v3 cursor pagination' implying it's for bulk listing, and explicitly says 'Use clickup_chat_channel_create to create new channels,' guiding when to use an alternative. However, it does not explicitly exclude use cases like retrieving a single channel, which is served by clickup_chat_channel_get.

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