check_ocr_status

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

With no annotations, the description discloses return information (status, address, path). It could mention idempotency or non-destructiveness, but the provided context is adequate for a read-only check.

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 well-structured with purpose, usage guidance, and return info in separate sections. It is concise, though the '节省 token 场景' line could be integrated more tightly.

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 no parameters and an output schema, the description covers the key return fields in plain language. It lacks details on error handling or potential network issues but is otherwise sufficient.

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?

No parameters exist, so the description naturally adds no parameter info. Schema coverage is 100%, meeting the baseline and earning a high score.

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 the tool checks the Umi-OCR service status, with a specific verb ('检查') and resource ('Umi-OCR 服务'). It distinguishes from siblings like 'quick_ocr_status' by providing context for usage before OCR tasks.

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?

Explicitly advises using this tool before important OCR tasks to confirm service availability and avoid token waste, providing clear when-to-use context.

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