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

With no annotations provided, the description carries the full burden and does: it discloses that images and scans go through OCR, that access requires a $0.012 USDC payment via x402 per call, and what the response looks like. Cost and payment mechanism are exactly the kind of trait an agent cannot infer from an empty annotation set.

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?

The contract-first sentence is front-loaded and every clause about field types earns its place. The trailing example output is truncated mid-object ('"Date'), which weakens an otherwise tight structure.

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?

No output schema exists, yet the description supplies an illustrative response payload, the extraction categories, the OCR caveat, and the per-call price. An agent has everything needed to decide to call it and to interpret what comes back.

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?

A single required parameter with 100% schema description coverage, so the schema already documents it fully. The description only restates the accepted input types ('PDF or image URL in'), matching the baseline for a well-covered single-param tool.

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 ('One call document parsing') plus an explicit input/output contract: 'PDF or image URL in, full text plus extracted fields out'. The enumerated document types and extracted field list separate it from narrow siblings like pdf_to_text and image_ocr.

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?

The 'one call' framing and the breadth of covered document types (invoices, receipts, statements, forms, scans) imply when to reach for this over a single-purpose extractor. It never names pdf_to_text or image_ocr as alternatives or states exclusions, so the routing still requires inference.

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