agent_read_channel

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

The description states it reads and decrypts messages and is restricted to members. With no annotations, the description carries full burden. It does not disclose ordering, pagination behavior, whether messages are deleted after read, rate limits, or any authentication details beyond membership.

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 short sentence with 10 words, very concise. No unnecessary information. Could be improved by breaking into two sentences for readability, but overall efficient.

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 tool with 4 parameters, no output schema, and no annotations, the description is minimal. It lacks details on message ordering, pagination (despite having a limit param), decryption behavior, and how the API key relates to membership. Unclear how it differs from sibling tools like agent_receive_messages. Not complete enough for an agent to use reliably.

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 the schema already explains all four parameters (api_key, channel_id, since, limit). The description adds no additional parameter meaning or usage hints beyond what the schema provides. 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?

Description clearly states 'Read decrypted messages from an encrypted channel' with a specific verb (read) and resource (decrypted messages). However, there is a sibling tool 'agent_receive_messages' that likely overlaps, but the description does not distinguish between them.

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?

Only mentions 'Only members can read' as a precondition. No guidance on when to use this tool versus alternatives like agent_receive_messages, agent_send_message, or agent_post_to_channel. No when-not-to-use or explicit context.

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