get_pdf_page_image

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that processing happens locally and that the output is a PNG image, though it does not discuss failure modes such as out-of-range pages.

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?

Two tightly written sentences with no waste. The core purpose is front-loaded, followed immediately by the key usage condition and alternative.

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?

The description covers the essential behavior for a PDF-page renderer: output format, source context, usage condition, read-only nature, and local processing. It is nearly complete, with only minor gaps around error behavior or output dimensions that the schema partly addresses via scale.

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%, so the schema already documents url, page, and scale with examples and bounds. The description adds cross-tool meaning by explaining that read_file reports the total page count, which helps the agent choose a valid page number.

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?

States a specific verb and resource: returns one PDF page from the Campus as a PNG image, and explicitly covers visual content that read_file cannot capture as text. This clearly distinguishes it from the sibling read_file tool.

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?

Names the alternative (read_file) and the exact condition for using this tool: diagrams, charts, formulas, and slides that read_file cannot capture as text. It also explains how to know which page to request by referencing read_file's reported total page count.

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