list_channels

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

With no annotations, the description carries the burden. It explains default types behavior and that limit caps at the API page size. It does not disclose pagination, rate limits, or authentication requirements, which are common for list endpoints.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second sentence adds crucial parameter details. Every sentence adds value with no redundancy.

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 output schema exists, return values are not needed. The description covers the main filtering behavior but misses explaining the 'workspace' parameter and pagination details beyond 'caps results at the API page size'. It is adequate but leaves 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 description coverage is 0%, so the description must compensate. It explains the 'types' parameter (comma-separated subset and default) and 'limit' (caps results), but omits any explanation of the 'workspace' parameter, leaving its meaning unclear 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 clearly states it lists channels in the workspace, specifying the verb 'list' and resource 'channels'. It hints at filtering by types and limit, but does not explicitly differentiate from sibling tools like search_channels, though the verb implies a full listing vs. search.

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 provides context on when to use it (list all channels) and a hint about default behavior (omitting DMs to keep responses short). However, it lacks explicit when-not-to-use guidance and does not mention alternatives such as search_channels for targeted queries.

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