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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's job is to add economics and workflow context; it does that by stating the call is free and is a pre-payment gate. It omits quote validity/expiry, rate limits, and authentication requirements, which would matter for a paid pipeline.

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?

Two tight sentences: first the value proposition and payload contents, then the handoff instruction. No filler and the key information is front-loaded.

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?

There is no output schema, so the description must name the return values, and it does (page count, route, final price, quote_id). For a simple one-parameter tool this is nearly complete; only quote lifetime and error/unsupported-input behavior are missing.

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?

Only one parameter and schema description coverage is 100% ('PDF URL'), so the schema carries the parameter burden and the baseline is 3. The description adds no format constraints (size limits, public URL requirement, redirect handling) beyond what the schema states.

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+resource ('free quote for PDF parsing') and enumerates exactly what the quote contains (page count, text/scan-OCR route, final price), which is far more than a restatement of the name. It implicitly separates itself from parse_document by positioning itself as the pre-payment step, though it does not explicitly distinguish itself from the similar-looking pdf_info or pdf_pages 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?

Gives a clear condition of use ('before any payment') and an explicit follow-up path: pass the returned quote_id into parse_document, including the endpoint hint. It does not spell out when this is unnecessary (e.g., if the caller already has a quote) or list non-PDF cases.

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