ocr_batch

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

No annotations are provided, so the description carries the full burden. It discloses processing behaviors such as auto_enhance, rotate (based on EXIF), and binarize, and mentions returns, but it doesn't describe limitations, error handling, or performance implications.

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 well-structured docstring with clear Args and Returns sections, front-loaded purpose, and no unnecessary prose. Every sentence contributes useful information.

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?

The description provides a good overview but lacks a detailed return structure (no output schema) and doesn't explain how the returned results are organized. Additionally, it doesn't position the tool relative to its siblings, leaving some usage context unclear.

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 Args section explains all five parameters with meaningful descriptions despite 0% schema description coverage. For example, output_format lists allowed values (plain/json/markdown/structured) and rotate specifies EXIF-based rotation. This fully compensates for the schema's lack of descriptions.

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 '批量 OCR - 对多张图像执行 OCR 识别' (Batch OCR - perform OCR on multiple images), using a specific verb and resource with batch scope. This distinguishes it from the sibling tools ocr_by_path, ocr_by_content, and ocr_by_url, which are likely for single images.

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 but does not explicitly state when to use this tool vs alternatives. It lacks a clear 'when not to use' or mention of sibling tools for single-image scenarios.

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