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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value on top: an 8-page per-call cap, pagination via prossimo_inizio, the caveat that OCR order may mix columns, and an explicit prompt-injection warning that the text is a source to study, not instructions to execute. It stops short of auth/error behavior, so 4 rather than 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?

Dense but front-loaded: the core action and the 8-page cap come first, then per-field semantics, then continuation, then caveats. Nearly every clause earns its place; the paragraph is long but there is little 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?

For a read-only, idempotent retrieval tool with an output schema already present, the description supplies everything an agent needs: input semantics, batch limit, pagination, and the fonte_id handoff to verify_quote. Return-shape details are correctly omitted since the output schema covers them.

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 0%, so the description carries the full burden and does so: inizio is defined as a character offset (0 = from start), caratteri with its 100-12000 range and 6000 default, area as [x0,y0,x1,y1] on a 0-10000 scale restricted to words inside the box, and fascicolo/pagina identified as coming from search. Every field of the nested PaginaDaLeggere object is explained beyond the bare schema.

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 ('Legge il testo OCR originale di una o più pagine') plus an explicit scope cap (fino a 8 in una chiamata), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from read_passages, view_scan or fetch, which is the only thing keeping 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 workflow hints: 'fascicolo e pagina (da search)' tells the agent this tool is downstream of search, and 'Per continuare una pagina lunga usare il suo prossimo_inizio' gives continuation guidance. However, it never states when to prefer read_pages over read_passages or view_scan, nor any exclusions, so the routing burden is left to inference.

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