ocr_image

Does the description disclose side effects, auth requirements, rate limits, or destructive 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?

描述简洁，先总述用途，再区分同族工具，最后说明参数和返回，无冗余内容。

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?

针对单一参数和简单返回值，描述充分解释了输入输出，无需额外补充。

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?

解释了image参数支持的类型（本地路径、URL、base64），超越了模式中仅字符串类型的定义，覆盖了参数。

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?

明确说明了OCR提取文字功能，并与recognize_image区分，使用了具体动词+资源（提取文字），场景清晰。

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?

通过对比recognize_image和列举适用场景（截图取字、票据录入等）提供了使用指引，但未明确说明何时不应使用。

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