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

With no annotations, the description carries the full burden and does disclose the two things an agent most needs: billing at €0.025 per page and the auth requirement (Bearer API key). It does not say what happens when a PDF has no text layer or no tables, nor whether errors are billed.

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 purpose, then use cases, then cost/auth, then a compact parameter list — every sentence carries information an agent needs and there is no 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?

An output schema exists, so return values need not be explained, and the description covers input formats, page scoping, pricing, and auth. Minor gaps remain around no-table/scanned-PDF outcomes and page limits, but nothing that would prevent a correct call.

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% and the schema declares no enums, so the description does all the work — it documents all three parameters with an example page range ('2-4'), the 'default all' behavior, and the format enumeration (json default | csv | markdown). It does not clarify that all parameters are technically optional/nullable or what happens if url is omitted.

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 description states a specific resource and output shape: 'Every table on the given pages as JSON rows, CSV file or Markdown', and the examples ('Bank statements, price lists, invoices with a text layer') make the target domain unambiguous. The 'with a text layer' qualifier implicitly separates it from OCR-style siblings, but no sibling is named explicitly.

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 clear usage context — text-layer PDFs, example document types, and per-page billing that matters for choosing page ranges. The 'text layer' condition acts as an implicit exclusion for scanned documents, but there is no explicit 'use ocr/pdf_text instead when…' routing.

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