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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds rich behavior: ~40,000 characters per page, rows tagged [letta]/[scartata], notebook dedup that skips already-read pages unless anche_viste=true, and partition semantics for piste_esatte. That is substantial context beyond annotations, though some terms remain cryptically defined.

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?

It is dense but front-loaded with the core continuation concept, and each sentence introduces a distinct behavior (pagination size, row markers, dedup, work-splitting, partition). Readability suffers from a single unbroken block of specialized jargon, but there is little pure filler.

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?

Output schema and readOnly annotations cover return values and safety, and the description explains pagination/marking behavior well. The main completeness hole is the undefined required 'piano' parameter plus reliance on output-side field names (elenco_prossimo, confronto_piste) without linking them clearly, leaving an agent to infer part of the contract.

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 coverage the description must carry all parameter meaning. It explains 'da' (start index from elenco_prossimo), 'anche_viste' (show already-seen pages with the mark), and 'piste_esatte' (partition of confronto_piste, zero-based indices, exact membership). However the required 'piano' parameter is never explained at all, a significant gap for the one mandatory argument.

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?

The first sentence states a specific verb+resource: 'Continua l'ELENCO di una ricerca' (continue the LIST of a research), scoped by a starting page number. This distinguishes it from research_continue (progressing the search) as a paginated results-listing operation. It loses a point for heavy undefined jargon (elenco_prossimo, quaderno, confronto_piste) and no explicit routing against its many research_* siblings.

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?

It gives concrete usage context: continue from 'da' using elenco_prossimo from the previous response, and 'per dividere il lavoro (anche fra sotto-agenti) si può chiedere qualunque tratto' explains how to split work. It stops short of naming alternatives/exclusions (e.g., when to use research_read or research_continue instead).

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