channel_read

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

Implies read-only behavior and mentions incremental pull, but with no annotations, it could be more explicit about idempotency or non-destructiveness. Does not cover error cases or behavior for missing channels.

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?

Two concise sentences: one for purpose, one for key usage hint. No fluff or 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?

Adequate for a simple read tool with output schema and well-documented parameters. Could mention ordering or when to use other channel tools, but overall sufficient.

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 100%, so baseline is 3. Description adds no extra meaning beyond the schema, only referencing the 'since' parameter.

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?

Clearly states the tool reads messages from a channel, using a specific verb and resource. Distinguishes from sibling tools like channel_send and channel_mentions.

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?

Mentions incremental pull via 'since' parameter, providing a usage hint, but lacks explicit guidance on when to use this tool versus alternatives like channel_mentions or meeting_read_messages.

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