ocr_text_paddle

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

Without annotations, the description carries the burden and does well: it discloses the return structure (per-line confidence, bounding boxes), the backend, cross-platform maturity, and the need for a specific package. It also notes performance characteristics (slower than Vision). Missing details on error handling or side effects, but the disclosed behavioral traits go beyond the schema.

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 concise and well-structured. The first sentence gives the core function and return values; the second paragraph adds backend context, comparison to Vision, and a requirement. Every sentence provides useful information without redundancy, and it is front-loaded.

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, no annotations, and 3 parameters with no schema descriptions. The description provides a clear purpose and some behavioral context, but it omits parameter semantics (lang, mode), accepted values, and return format details. This is insufficient for fully correct invocation, especially given the absence of structured metadata.

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 description coverage is 0% and the description does not explain any of the three parameters. While 'path' is implied by 'image', the meanings of 'lang' (language) and 'mode' (e.g., 'base') are not described. The description fails to compensate for the absence of schema descriptions, leaving the agent without necessary parameter semantics.

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's purpose with a specific verb and resource: 'Extract text from an image.' It also details return values (full text, per-line confidence, bounding boxes) and specifies the backend ('paddle'), distinguishing it from sibling tools like ocr_text_vision or layout/table OCR variants.

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 provides comparative guidance: 'Wider language support than Vision, but slower' indicates when to prefer this tool over the Vision-based alternative. It also mentions the requirement for the PaddleOCR Python package, which aids in setup. It does not explicitly exclude layout/table tools but the text-extraction focus is clear.

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