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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behavior beyond the schema: cost (1,25 ₽ per 10 photos / 10 MB), that all photos are merged into a single output, and the semantic difference between txt (lines as in the photo) and docx (paragraphs). It omits things like async behavior or failure handling, but covers the operational essentials.

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 block is front-loaded (what it does, then cost, then per-parameter notes) and every line carries information an agent needs. No filler or repetition.

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?

With an output schema present, return values need no explanation, and the description covers purpose, pricing, input constraints, per-parameter semantics and output format behavior. Nothing required to invoke it correctly is missing.

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 fully compensates: file_urls is defined as public URLs with the allowed image formats, languages lists the four supported codes and the default ['rus','eng'], and format explains txt vs docx and the default. All three parameters gain meaning not present in the schema.

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 verb and resource: OCR of text on photos/images, with the concrete output ('все фото — в один TXT или DOCX'). The scope ('фото и картинках') and the reference to ocr_pdf make it easy to separate from the many pdf_*/image-conversion siblings.

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?

Usage is implied through the accepted input formats (JPG, PNG, WEBP, HEIC, TIFF, BMP) and the pricing parallel with ocr_pdf, but there is no explicit when-to-use/when-not or a direct routing sentence such as 'use ocr_pdf for PDFs'. Adequate but inferential.

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