list_channel_messages

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

With no annotations provided, the description must disclose behavioral traits. It merely states 'list recent messages' without revealing ordering (e.g., newest first), pagination behavior, rate limits, or whether replies are included. A read-only hint would be helpful.

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 sentence, concise but lacking structure. It front-loads the purpose but omits necessary details like ordering or pagination, which could be included without significant bloat.

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 tool has only 3 parameters with full schema coverage and no output schema. The description is functional for a simple list operation, but additional context about the return format or required permissions would improve completeness.

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, with clear parameter descriptions for 'top', 'team_id', and 'channel_id'. The tool description adds the word 'recent' but does not further clarify the relationship between 'top' and the ordering. Baseline 3 applies as schema already carries the burden.

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 'List recent messages in a channel' clearly specifies the action (list) and resource (messages in a channel). It distinguishes from sibling tools like list_chat_messages which target different conversation contexts. However, it could be more specific about 'recent' and whether it returns top-level or threaded 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?

No guidance is given on when to use this tool versus alternatives such as search_messages (which can search across channels) or list_chat_messages (for chat conversations). Users are left to infer the appropriate context from the tool name alone.

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