baidu_ocr_numbers

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

No annotations are provided. The description includes pricing and free quota, which is helpful, but it does not disclose whether the tool is read-only, what limitations exist (e.g., only digits), or expected output format. This is insufficient behavioral transparency.

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 concise, consisting of a single line with a tag, purpose, and pricing. It is front-loaded and contains no superfluous text. However, it is in Chinese, which may be a minor accessibility issue.

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 tool has no output schema, so the description should explain what the tool returns. It does not. Given the complexity of multiple sibling OCR tools, the description lacks details on expected input format and return value structure, making it incomplete.

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 only parameter 'image' is described in the schema as '图片URL' (image URL). With 100% schema description coverage, the baseline is 3. The description adds no additional semantic meaning beyond the schema, such as image format requirements or expected content.

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] Digit recognition' clearly indicates the tool's purpose of recognizing numbers from images via OCR, distinguishing it from sibling tools like general OCR or handwriting OCR. However, it lacks an explicit verb like 'recognizes' or 'extracts', making it slightly less explicit.

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 guidance is provided on when to use this tool versus alternative OCR tools. Given the large number of sibling OCR tools (e.g., baidu_ocr, baidu_ocr_handwriting), the lack of usage instructions makes it difficult for an agent to select the correct tool.

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