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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. Beyond that, the description adds real behavioral context: ordering (newest first), scope (per-platform, default all), what a complaint_hint means, and whether a human already took over the thread. That extra context justifies a 4.

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?

Three dense sentences with the scope and ordering front-loaded and no filler. The middle sentence's field enumeration is long but earns its place by describing the return shape in the absence of an output schema.

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 read-only listing tool with no output schema, the description enumerates the item fields (platform, chat_id, chat_uuid, account_id, name, last message, time, complaint_hint, takeover status), which is exactly what the missing output schema would have provided. Only `limit` and pagination behavior are unaddressed.

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?

With 0% schema description coverage, the description carries the burden and does most of it: it explains `days` (time window), `platforms` (ig|fb|tw|wp, default all) and `only_hinted` (filter to hinted items). Only `limit` is left unexplained, though its meaning is largely self-evident from the name.

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 concrete verb and resource: read conversations awaiting an answer within the last `days`, newest first, across ig|fb|tw|wp. It also clarifies the tool is not a classifier (the 'complaint_hint' is a match, not a verdict). It does not explicitly distinguish itself from siblings like chats_collect_sales_signals or list_chats, which keeps it from a 5.

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?

Usage is implied through 'Read the texts yourself to decide which are complaints' and the only_hinted toggle, which tells the agent how to narrow results. However, there is no statement of when to prefer this over chats_collect_sales_signals or list_chats, and no prerequisites are mentioned.

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