ocr_parse_multi

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Parse multiple images using Unlimited-OCR', which adds no behavior beyond the tool name itself; there is no mention of output format, side effects, network usage, or limitations.

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 description is a single crisp sentence with no filler, front-loading the core action. It is concise, though it sacrifices necessary detail for brevity.

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?

Given five parameters, no annotations, no output schema, and no parameter-level descriptions, this one-sentence description is grossly incomplete. An agent cannot know how to set or interpret the optional parameters, what the tool returns, or when to invoke it instead of siblings.

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 only loosely clarifies that image_paths holds multiple images/pages. The four optional parameters (max_length, output_dir, ngram_window, no_repeat_ngram_size) are entirely undocumented, leaving the agent to guess their meaning.

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?

Description states a specific action ('Parse') and resource ('multiple images'), and the '(multi-page)' qualifier plus sibling names (ocr_parse_image, ocr_parse_pdf) make it clearly distinct. Mentioning 'Unlimited-OCR' also adds concrete context.

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?

Use case is only implied: 'multiple images' and 'multi-page' suggest it is for bulk/page-wise OCR, but there is no explicit guidance on when to choose this tool over ocr_parse_image or ocr_parse_pdf, nor any exclusion criteria.

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