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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add context — and it does: ordering by oldest wait, inclusion of a 'why' reason, topic, and per-topic counts. No return format details beyond that, which is acceptable since no output schema exists.

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 ordering and payload details are packed in efficiently, though the run-on 'with why and its topic, and the count per topic' reads awkwardly.

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 two-parameter read tool with no output schema, the description covers the essential return shape (reason, topic, per-topic counts) and ordering. The only real gap is the undocumented limit parameter's effect on results.

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 only 50%: brand is well documented in the schema, but limit carries no description. The description adds nothing about either parameter — no explanation of what limit limits or whether it truncates the list, which matters because per-topic counts could be affected.

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 resource — chats waiting for a person — with explicit scope ('Every chat'), and the ordering ('oldest wait first'). An agent can distinguish it from list_chats or search_chats by the 'needs a person' qualifier, though no sibling is named.

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 name and description imply the use case (surfacing chats awaiting a human reply), but there is no explicit when-to-use / when-not-to-use guidance and no mention of list_chats, search_chats, or read_chat as alternatives once a chat is picked.

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