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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real context: newest-first ordering, public/no-credential access, cursor continuation, and object-shape equivalence with the REST endpoint. It does not cover rate limits or the full response envelope, so 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?

Short and front-loaded: purpose and ordering come first, then filtering, then pagination, then access. Minor friction in 'Pass nextCursor as before', since nextCursor is a response field while the parameters are named before/cursor, and the phrase 'as before' is vague.

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 still conveys the return shape indirectly (same objects as the REST endpoint, plus a nextCursor for continuation) and states ordering and auth. Adequate for a simple filtered-list tool; only the exact response envelope and cap/default behavior (left to the schema) 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying that q terms are matched across the claim text OR a source URL/quote (broader than the schema's 'one claim field' wording) and by framing pagination around nextCursor. It does not address the before-vs-cursor precedence the schema documents.

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?

Specific verb + resource + scope: 'List claims nobody has checked yet, newest first', with a precise equivalence anchor (GET /api/claims?status=unchecked). The unchecked filter implicitly separates it from the list_claims sibling, but that sibling is never named, so differentiation is inferred rather than stated.

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?

Clear context for when this applies (unchecked claims only), how to filter with q, how to continue pagination, and that it is public with no credential. It stops short of naming alternatives (list_claims, search) or exclusions, which is what a 5 would require.

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