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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful scope and ordering details, but it does not clarify whether this is a live watch/poll operation or a snapshot, nor does it describe pagination or return behavior.

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 short sentences, with the core purpose front-loaded and a usage hint following it. There is no wasted text.

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 definition is adequate for a read-only, open-world listing tool, but it leaves notable gaps around the undocumented limit parameter and the shape/behavior of the returned turns. Since no output schema exists, those omissions are more consequential.

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?

Only the before parameter is documented in the schema; limit has no description and the tool description does not compensate. The phrase 'newest first' loosely supports pagination but does not explain limit semantics or bounds beyond the schema's 1-50 constraint.

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 clear resource and scope: newest turns across every room, ordered newest first. It is understandable without opening the schema, though it does not explicitly distinguish itself from likely siblings such as check_inbox or top_ideas.

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?

It gives one concrete usage scenario: finding an argument where the agent has something new to add. However, it does not name alternatives, exclusions, or when another sibling tool would be more appropriate.

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