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

readOnlyHint already covers safety, yet the description still adds real behavior: results are ordered newest first, closed cases are excluded by default, and the response may carry an Attack Mode suggestion with a price. It also clarifies that Attack Mode is never entered without the agent, which is meaningful for a read tool that surfaces a mutation path. Gaps remain on pagination behavior for limit/before_id.

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?

Front-loaded with what the tool returns and avoids filler sentences, but the semicolon-chained phrasing is dense and the clause explaining 'next' and 'the words they can say to you for it' is wordy. Readable once, but harder to parse than necessary.

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?

With no output schema, the description does list returned fields and the Attack Mode side-channel, which is the right burden to carry. It omits pagination semantics (default 100, max 200, before_id) and tier meaning, which an agent needs to page correctly or filter usefully.

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 20% (only 'company' is documented), so the description must compensate. It explains include_closed, but leaves the tier enum values (strong/arguable/candidate), limit, and the before_id cursor entirely undefined in both places, which is a substantial gap.

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: lists the company's reviews that RepuTend flagged as disputable or worth a look, and names the fields returned (state, tier, category, next). It is distinguishable from most siblings but doesn't clarify how it differs from list_review_triage, which sounds adjacent.

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?

Gives conditional guidance for closed cases ('Closed cases only with include_closed') and instructs to surface the 'next' text to the user when non-null. It also routes Attack Mode actions to quote_attack_mode and set_attack_mode. However, there is no explicit statement of when to pick this versus list_review_triage or get_case.

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