ocr_document

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

The description claims 'Read-only', but annotations set destructiveHint=true, which contradicts the claim. This contradiction undermines trust and provides no additional behavioral context beyond the misleading statement.

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 two sentences with no wasted words. It is front-loaded with the core action and provides immediate guidance on usage context.

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?

While the description covers purpose and usage, it lacks information about the output format or return value. The annotation contradiction also reduces completeness. For a tool with only one required parameter and no output schema, more detail about 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?

The input schema has 100% description coverage for all three parameters (filename, language, page). The description adds no extra parameter semantics; it only mentions system dependencies. Baseline 3 is appropriate as the schema already defines the parameters.

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 performs OCR text extraction on a PDF, bypassing normal text extraction. It specifies the resource (PDF) and the action (Force OCR), and distinguishes it from read_document by describing when to use it.

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 explicitly says to use this tool when read_document returns garbled or empty text from a scanned PDF, providing clear context. It also mentions system dependencies (tesseract and pdftoppm), guiding the agent on prerequisites.

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