ocr_table_paddle

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

With no annotations, the description carries the full burden. It discloses several behavioral traits: CPU-based execution ('PaddleOCR CPU'), cross-platform maturity, language support breadth relative to Vision, speed trade-offs, and a dependency. It doesn't cover error behavior or side effects, but for a read-only OCR extraction tool, these are less critical, and the provided details are meaningful.

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 compact and front-loaded with the primary purpose. The second sentence adds targeted context about the backend, performance, and dependency without redundancy. Every piece of information earns its place, and the whole is easily scannable.

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?

Despite having a clear purpose and some backend context, the description leaves major gaps: it does not explain the 'mode' parameter, which is crucial for understanding extraction behavior, and it does not describe potential failure modes or output details beyond saying 'structured CSV/JSON.' With no output schema and no annotations, the overall picture is incomplete for effective tool 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?

Schema description coverage is 0%, so the description must compensate, but it does not. The parameters (path, lang, mode) are not explained. The only indirect hint is 'Wider language support,' which implies the lang parameter, but mode remains entirely unexplained. This is a significant gap for a tool with three parameters, especially since mode has a default and may control extraction behavior.

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 opens with a specific verb+resource: 'Extract tables from an image.' It clearly states the output format (CSV/JSON) and names the backend ('paddle'), which differentiates it from sibling tools like ocr_table_vision and ocr_table_paddleocr_vl. The added comparison to 'Vision' reinforces its unique position.

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 context for when to prefer this tool: 'Wider language support than Vision, but slower.' This is a clear trade-off, and it also notes a prerequisite ('Requires PaddleOCR Python package'). However, it doesn't explicitly say when not to use it or mention alternatives beyond Vision, so it falls short of a 5.

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