batch_ocr

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

With no annotations, the description must convey behavior. It explains the input format (glob or JSON list) and return format (JSON with count and results), which is essential. However, it does not disclose potential side effects, concurrency limitations, or error handling, leaving gaps in behavioral understanding.

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 extremely concise: two sentences with no wasted words. It front-loads the purpose ('OCR many images') and packs essential parameter and output format details into the second sentence.

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 3 parameters, 1 required, and no annotations, the description provides input/output format basics but omits engine options, language support, performance considerations, and error behavior. The output schema exists but the description still adds the return structure, making it adequate but not comprehensive.

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 should compensate. It explains the 'paths_or_glob' parameter format in detail but provides no semantics for 'engine' or 'lang' parameters, which have defaults but no description. Only one of three parameters is adequately documented.

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 starts with 'OCR many images,' which clearly states the tool's purpose as a batch OCR operation. It distinguishes itself from siblings like 'ocr_image' (single image) and 'ocr_pdf' (PDF).

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?

The description implies usage for multiple images via 'many images' and the glob/list input, but it does not explicitly guide when to use this tool versus alternatives like 'ocr_image' for single images or 'ocr_pdf' for PDFs. No when-not-to-use or exclusion criteria are provided.

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