OCR - Text from Image/PDF

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the description does not contradict them. The description adds that OCR uses Tesseract, which is useful context. However, it does not disclose limitations (e.g., image quality requirements, PDF page handling) that could affect 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?

The description is a single sentence (about 10 words) that is front-loaded with the core action. No wasted words.

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 moderate complexity (3 params, no output schema, no nested objects), the description is largely adequate. It covers the main purpose and technology (Tesseract). Minor gap: no mention of return value format, but since no output schema exists, some guidance on what the tool returns would be helpful.

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 100%, so parameters are well documented in the schema. The description does not add extra meaning beyond what the schema provides. Baseline 3 is appropriate as schema does heavy lifting.

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 specifies the verb 'extracts text' and the resource 'images (JPG/PNG/BMP/TIFF) and PDFs' using OCR, and the title 'OCR - Text from Image/PDF' further clarifies. It distinguishes this tool from siblings, none of which perform OCR.

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 implies use for extracting text from images/PDFs via OCR. However, no explicit guidance is given on when to use this tool vs alternatives (e.g., fc_read_file for text files). Context signals show 30+ sibling tools, but no exclusions or alternative references.

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