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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds significant behavioral context: returns rendered JPEG screenshots, caps at 10 pages per call, requires pagination via 'has_more' and 'next_start_page', and mandates scanning all pages before answering. It also notes the pip install prerequisite, which is useful for runtime setup.

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 dense but front-loaded with the primary use case. It uses a clear structure: when to use, what it returns, limitations, and a mandatory workflow. Every sentence serves a purpose, and the critical pagination rule is highlighted with 'ALWAYS' and 'MUST.' No filler or redundancy.

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 paginated rendering, the description fully covers the required workflow, including the loop condition, how to read structuredContent, and the requirement to complete scanning before any action. The output schema is not displayed here, but the description compensates by explaining the response semantics (has_more, next_start_page).

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 coverage is 100% with descriptions for all parameters. The description adds operational semantics by explaining how to use start_page and count in the pagination loop (start from 1, use next_start_page, respect the 10-page cap). This goes beyond the schema's simple default and type info.

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+resource: 'visually inspect PDF pages to identify content that cannot be detected from text alone.' It explicitly differentiates from siblings like view_pdf and get_pdf_info by focusing on visual elements (logo, photograph, watermark, QR code).

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 explicit 'when to use' context ('Use this when you need to visually inspect PDF pages...') and gives detailed step-by-step pagination instructions. It does not explicitly name alternative tools or when-not-to-use scenarios, but the context strongly implies the tool is for visual content only, so it earns above baseline.

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