ocr_parse_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals only that OCR is used; it does not mention whether the tool writes output files, what the returned data looks like, processing limitations, or side effects. This is nearly as opaque as a tautology.

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 text is brevity itself at a single sentence, so it earns some credit for front-loading the core action. However, brevity here is under-specification: the sentence lacks any functional detail and is too sparse to guide correct invocation.

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 tool with six parameters, no output schema, and no annotations, this description is severely incomplete. The agent cannot determine inputs beyond pdf_path, cannot predict output format, and cannot assess risk or resource usage. A minimally viable description would at least outline what 'parse' returns and what output_dir is for.

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 description mentions no parameters at all. Six parameters exist, including dpi, max_length, output_dir, and ngram_window, but the agent receives no hints about their meaning, defaults, or relationships. The description does absolutely nothing to compensate.

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 action ('Parse'), a clear resource ('a PDF document'), and the method ('using Unlimited-OCR'). The noun phrase distinguishes this from sibling tools named for images or multi-document parsing, though it does not explicitly name the alternatives.

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?

No guidance is given about when to choose this tool over ocr_parse_image or ocr_parse_multi, nor about preconditions like file paths or OCR suitability. The description simply states what it does, leaving all selection logic to inference.

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