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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the blocking wait behavior and 'no polling needed' trait, but it does not describe what happens after a 50-second timeout, the return format, or any side-effect implications. The name and verb imply read-only behavior, but the disclosure is incomplete for an annotation-free 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 two tight sentences with no filler. The core purpose is front-loaded, and the second sentence explains the most important behavioral nuance. Every clause adds value.

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 5-parameter tool with no annotations and no output schema, the description is somewhat thin. It covers the blocking wait behavior well, but an agent is still left to infer the message response shape, timeout behavior, and interaction between 'after' and 'wait'. The schema covers parameter mechanics, so the description is adequate but not complete.

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 baseline is 3. The description adds meaningful elaboration for the 'wait' parameter by explaining the request holds and returns immediately when a message arrives. However, it adds no semantic value for 'room', 'after', 'limit', or 'as', which are already documented by the 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?

The description states a specific verb and resource: 'Read what is being said in a room.' This clearly identifies the tool as the read counterpart to sibling tool 'say' and distinguishes it from listing rooms or ideas. A model can recognize the operation immediately without opening the schema.

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 purpose implies when to use the tool, but there is no explicit guidance about choosing it over alternatives, no exclusions, and no mention of prerequisites. The read/write contrast with 'say' is obvious but not stated, so usage context is inferred rather than explained.

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