read_pdf_as_images

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

With no annotations, the description fully discloses behavior: images are base64 encoded, return structure includes page number, dimensions, format, and truncation info. It explains the max_total_bytes_mb limit and that quality only applies to jpeg, giving agents full awareness of output characteristics and constraints.

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: a concise summary sentence followed by Args and Returns sections. Each sentence adds essential information without redundancy. Despite length, it is efficiently organized and front-loaded with the core purpose, making it easy for an agent to scan.

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 complexity of 6 parameters and no annotations, the description thoroughly covers all inputs (including edge cases like mixed page formats) and outputs (including truncated and warning fields). The output schema exists, but the description still explains return elements, making the tool fully understandable.

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 0% description coverage, so the description provides all parameter semantics. It explains file_path requirement, pages format (with examples), dpi trade-offs, image_format defaults, quality range and exclusive jpeg applicability, and max_total_bytes_mb. This adds significant value beyond the raw schema.

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 converts PDF pages to base64 images, specifies the verb and resource, and explicitly mentions suitable scenarios (retaining layout, charts, formulas), distinguishing it from sibling tools like read_pdf_as_text.

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 on when to use the tool (scenarios needing original layout) and includes detailed parameter usage guidance. It does not explicitly exclude cases or name alternatives, but the purpose and sibling list imply when to choose this over text or other extraction tools.

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