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

No annotations are provided, but the description discloses that the quote is free, includes page count/route/price, and returns a quote_id. It accurately communicates the tool's behavior without contradictions. Minor gap: no mention of side effects, but for a quote tool this is sufficient.

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 sentences with no fluff. The first sentence states the purpose and quote contents; the second provides integration guidance. Every word contributes value.

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 single-parameter tool with no output schema, the description explains the purpose, what the quote includes, and how to use the result. It is complete enough for an agent to select and invoke the tool correctly, though it doesn't detail the output format.

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?

The schema covers 100% of the parameter (url) with a clear description. The tool description does not add additional meaning about the parameter itself, so the baseline of 3 is appropriate.

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 clearly states it provides a free quote for PDF parsing, listing specific quote contents (page count, route, exact final price). It distinguishes from sibling tools by explicitly referencing parse_document, indicating the quote is a precursor to parsing.

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 explicitly says 'before any payment' and instructs to use the returned quote_id with parse_document, providing a clear workflow. This implicitly defines when to use this tool versus the parse_document alternative.

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