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

With no annotations, the description carries the full behavioral burden. It usefully discloses the OCR page cap (100 pages) and that OCR is billed like ocr_pdf, plus the requirement that file_url be public, but it says nothing about input size limits, failure behavior, or what happens to the original file.

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?

Three short lines, front-loaded with purpose followed by per-parameter notes; every sentence carries information. Slightly terse on the parameter lines, but 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 purpose, both parameters, OCR trigger, cost, and a page limit. It stops short of naming the sibling it overlaps with (ocr_pdf, pdf_to_txt) and omits any input-size guidance.

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 must compensate, and it does: file_url is clarified as a public URL, and ocr is explained with its trigger condition, supported languages, page limit, and cost. That is substantial meaning beyond the raw boolean/string schema, though neither param's format constraints (e.g. URL format, defaults) is fully spelled out.

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 names a specific verb and resource (converts PDF to Markdown .md) and even enumerates the structures preserved (headings, lists, tables, links, bold/italic), which clearly separates it from pdf_to_txt and pdf_to_word. It does not explicitly name or route against those siblings, so it falls just short of the top tier.

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 a clear use context (for neural networks, knowledge bases, documentation) and a conditional instruction for the ocr flag (use it for scans without a text layer, Russian and English). No explicit when-not or named alternative is given, so 4 rather than 5.

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