read_messages

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

With no annotations, the description carries the burden of transparency. It reveals that the tool blocks via long-polling and consumes (likely deletes) messages, which are important behavioral traits. However, it omits details about timeout handling, idempotency, or what happens when no messages are available.

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, front-loaded sentence that immediately communicates the core behavior. There is no filler or redundant information.

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 4 parameters, no annotation support, and no parameter descriptions. The description fails to explain how to use the parameters, the meaning of consuming messages, or how this fits with joining topics. The output schema exists but is not shown, so the description is insufficient for safe and correct invocation.

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 coverage is 0% and the description mentions no parameters. The only indirect hint is 'joined agent', which relates to join_token, but timeout_ms, verbosity, and max_messages are entirely unexplained. The description adds minimal value for parameter understanding.

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 specifies concrete actions (long-poll, read, consume) on a clear resource (pending messages) for the joined agent. This clearly distinguishes it from send_message and other topic management tools.

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 clear context that this tool is for receiving/consuming pending messages, which implicitly tells when to use it versus send_message. It lacks explicit exclusions, but the intent is obvious from the verb and resource.

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