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

Annotations already declare readOnlyIdempotent/non-destructive, but the description adds substantial context beyond them: a hard result cap (at most 50), ordering (latest first), and an admin auth requirement plus a feature gate. It doesn't cover pagination continuation or return shape, hence not a 5.

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 dense sentences, front-loaded with the core purpose and constraint; no filler. The parenthetical listing of every filter dimension is slightly redundant given the schema, keeping it just under a 5.

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, no-required-param tool with no output schema, the description covers the key operational facts an agent needs (scope, cap, ordering, auth/feature gates). It leaves ambiguous what happens past the 50-result window, but overall is complete enough to call correctly.

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 82%, so the schema already documents the filter parameters. The description enumerates the filter dimensions (opening/closing sentiment, risk flag, frustration, handler, agent, inbox, team) but largely restates what the schema says rather than adding new semantics like time format or combined-filter behavior.

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 (List) and resource (conversations) and immediately scopes it as 'the conversations behind a cell of the sentiment report', which cleanly separates it from get_sentiment_report and generic listers like conversation_list. An agent can tell what it returns 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 description gives clear context (drill-down from the sentiment report; 'same range rules as the report') and upfront constraints (Administrators only, requires ai_decisions feature). It does not explicitly name an alternative tool or a when-not condition, so it falls short of the 5 bar.

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