read_chat

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions that the tool 'listens for a while' and returns messages, and explains the seconds parameter. However, it does not clarify whether the call is blocking, what happens if no messages arrive (e.g., returns empty array or waits indefinitely), or if it reads existing messages first. These are moderate gaps for a listening tool.

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 exceptionally concise: two sentences for purpose and one for parameter. No wasted words, front-loaded with the core action. Every sentence earns its place.

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 is simple (one optional parameter) and has an output schema (not shown but present). The description covers the essential behavior and parameter. An agent has enough to use the tool correctly. No additional information is needed for this low-complexity 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 coverage is 0%, so the description must explain the parameter. It does so clearly: 'seconds: How long to listen (default 15)'. This adds context beyond the schema's default and type, making the parameter's role explicit. The description fully compensates for the low schema coverage.

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 clearly states the verb 'Listen' and the resource 'incoming chat messages', and explicitly connects it to the LLM's need to answer user input. It naturally distinguishes from sibling 'say_in_chat' which sends 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?

The description implies the usage context (when the LLM needs to respond to user chat), but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools. The purpose is clear enough for an agent to infer use, but lacks direct comparative guidance.

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