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

No annotations provided, so description carries full burden. Describes ordering (newest first) and wait behavior. Does not disclose potential empty response behavior, rate limits, or authentication details beyond schema. Adequate but could be more thorough.

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 sentences, front-loaded with core action. First sentence states purpose and data fields; second adds usage tip. No wasted words, highly 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?

With no output schema, description lists return fields (method, path, query, headers, body). Covers key aspects: ordering, wait functionality, data fields. Minimal gaps like pagination or error states, but adequate for a simple read tool.

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 covers 100% of parameters with descriptions. Tool description adds practical context: for 'wait', explains use case; for 'since', recommends using timestamp of last seen request. Adds value beyond 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?

Clearly states 'Read the HTTP requests captured by a bin (method, path, query, headers, body), newest first.' Identifies verb (read), resource (requests from bin), and attributes. Differentiates from siblings clear_bin and create_bin.

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?

Provides context: 'Set wait to block until a request arrives — ideal for 'trigger then assert' with no polling loop.' Implies usage for retrieving requests while siblings handle clearing/creation. No explicit when-not instructions but adequate.

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