image_ocr

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 mentions Tesseract OCR, which gives a hint about behavior, but does not disclose limitations (e.g., supported image formats, accuracy on different image types, or rate limits). The description covers input parameters but lacks deeper behavioral context that would help an agent judge reliability or side effects.

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 compact docstring that front-loads the core purpose and then lists parameters in a clear, structured format. Every sentence provides value; there is no fluff or repetition. It is appropriately concise and well-organized.

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 that an output schema exists, the description need not explain return values. It covers all parameters and includes practical details like URL support and language code formatting. However, it does not mention any constraints on image inputs (e.g., size limits, file type support) or performance characteristics, which would enhance completeness for a tool with no annotation context. Overall, it is nearly complete for typical use.

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 schema has 0% description coverage, but the description provides a detailed 'Args' section explaining each parameter (source, language, max_chars) including examples for language codes and the meaning of max_chars. This adds significant meaning beyond the bare schema fields, fully compensating for the lack of schema 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 the verb 'Extract' and the resource 'text from an image', and specifies the OCR engine (Tesseract). This distinguishes it from siblings like pdf_ocr (which handles PDFs) and other image tools that do not perform OCR. The purpose is unambiguous.

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 images but does not explicitly state when to use this tool over alternatives such as pdf_ocr or other image processing tools. There is no reference to alternatives or exclusion criteria, leaving the agent to infer context from the name and siblings. This is adequate but not explicit.

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