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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one real constraint (rooms must be same-account) and implies a read operation, but says nothing about ordering, whether results are paginated or capped, what backfill/sinceEventId do behaviorally, or what the response looks like.

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?

A single front-loaded sentence with no filler; the default behavior comes first and the alternative mode second. It is short to the point of under-specification rather than padded, so brevity itself is not the flaw.

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?

Placeholder check.

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 only 25%, so the description must compensate and largely does not. It clarifies roomId's meaning (a same-account room) but leaves backfill (1-200) and sinceEventId entirely unexplained, which are the two parameters most likely to be misused.

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?

States a specific verb and resource ('Return the messages') and scopes it to the current call session, with a fallback mode keyed on roomId. It does not name or contrast with siblings like foragent_listen or foragent_wait_for_next_message, so an agent must infer the boundary itself, but the core purpose is unambiguous.

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 parenthetical implies the when-to-use split: omit roomId to read the current call, pass roomId to read a same-account room. There is no explicit guidance on when to prefer this over foragent_listen or foragent_wait_for_next_message, and no stated exclusions or prerequisites.

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