baidu_ocr_business_license

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

No annotations provided. Description only includes pricing and quota, but does not disclose behavioral traits like read-only nature, error behaviors, or required permissions. The agent lacks insight into side effects or limitations.

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 very short (one sentence), which is efficient, but it omits valuable information. It is not overly verbose, but the brevity comes at the cost of clarity in usage and behavior.

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 tool has no output schema and only one parameter, the description should at least indicate the expected output format. It does not. The pricing info is helpful but insufficient for complete understanding.

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 coverage is 100% with a single parameter 'image' described as '图片URL'. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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 '营业执照识别' (business license recognition), a specific OCR task. It distinguishes itself from sibling OCR tools like baidu_ocr, baidu_ocr_bankcard, etc., by specifying the document type.

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 on when to use this tool versus alternatives like baidu_ocr_accurate or baidu_qianfan_ocr. No context on prerequisites or expected image quality.

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