baidu_ocr_webimage

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

With no annotations provided, the description must fully disclose behavioral traits. It reveals the cost per call and that it handles web images (URL input), but fails to mention output format (e.g., text, confidence scores), error conditions, or whether it supports concurrent calls. The behavioral disclosure is inadequate.

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 concise (one line), but it omits essential details like what the tool returns. While it includes cost info efficiently, the brevity compromises completeness. A balanced description would be slightly longer to cover core functionality.

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's simplicity (1 parameter, no output schema) and many similar siblings, the description should clearly explain the tool's unique purpose and behavior. It partially covers purpose (web images) but lacks details on output, usage scenarios, and limitations, making it incomplete for effective agent invocation.

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 fully describes the single 'image' parameter as a URL (图片URL) with 100% coverage. The description adds no additional semantic value beyond restating it handles web images. Baseline score of 3 applies since schema already covers the parameter meaning adequately.

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 it's for OCR on web images (网络图片文字识别), providing a specific verb (recognize) and resource type (web images). However, it does not explicitly differentiate from the many sibling OCR tools (e.g., baidu_ocr_accurate, baidu_ocr_handwriting), relying on the 'webimage' part of the name to imply distinction.

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 includes cost information ($0.02/call) and a free quota (5/5 today), which hints at usage conditions but does not provide guidance on when to use this tool over alternatives, such as when to choose webimage versus other OCR tools for different image types or accuracy needs.

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