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

With no annotations, the description carries the full burden, but it only reveals that the tool is pay-per-use at a stated price. It does not disclose input format, supported languages, return value, processing behavior, or any safety/authorization considerations. This is insufficient for an agent to predict the tool's behavior.

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 short and front-loaded, with the core function stated first and pricing in a bracket. It is free of fluff, which earns high marks for conciseness. However, the brevity sacrifices necessary detail, so it is not a model of effective structure.

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 there is no output schema, no annotations, and only a vague one-parameter schema, the description should explain what the tool returns, how to supply input, and which languages it supports. It does none of this, leaving critical gaps for an agent deciding whether to invoke it. The presence of many OCR sibling tools increases the need for distinguishing context.

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 input schema contains one parameter with a generic description 'pipeline input', and while schema coverage is 100%, the description adds no concrete meaning about the parameter. The description's mention of OCR implies the input is some document/image to process, but this is indirect and not actionable. Baseline 3 applies due to full schema coverage.

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 'ocr specialized for multi language' states the tool's domain (OCR) and a specialization, but it largely restates the tool name without specifying what the tool does with the input or how it differs from plain 'ocr' or 'vision-multi-language'. It is more a label than a functional definition.

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?

No usage context is provided; there is no mention of when to choose this tool over sibling tools such as 'ocr', 'ocr-batch', or 'vision-multi-language'. The only added signal is the cost note, which is not a usage guideline. The description relies on the name to imply multilingual use.

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