ocr_file

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds valuable context: tier-based file size limits (1MB free, 5MB pro), EU endpoint for GDPR, and optional saving to txt/json. However, it does not explicitly state that the file is uploaded to a third-party API or describe return behavior when no output_path is given.

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 three sentences with no fluff. It front-loads the primary action and packs in essential constraints (formats, size limits, GDPR, optional output) efficiently.

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 the complex 11-parameter schema and no output schema, the description covers the core workflow (local input, API, optional saving) well. It misses an explicit statement about what the function returns when no output_path is provided, but 'Extract text' implies the text is returned, so the gap is minor.

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 100%, so each parameter already has detailed descriptions (e.g., tier explains 1MB/5MB limits, output_path explains saving). The tool description adds only supported file formats, which is marginal. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Extract text from a local image or PDF file using OCR.space API', specifying the action, resource, and method. It also lists supported formats, making it distinct from sibling tools like ocr_url which handles URLs.

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 provides clear context that this tool is for local files, distinguishing it from URL-based tools. However, it does not explicitly name alternative tools (e.g., 'use ocr_url for remote files') or specify when not to use it, so it stops short of full guidance.

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