Render paper page

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior — the PNG output format, the scale range/default, and the 2400 px longest-edge cap that can silently downsample output at high scales. It does not mention rendering latency or failure modes for 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 short clauses, front-loaded with the core action and output format, followed by constraints. No filler, and every clause carries usable information for invocation.

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?

For a read-only, single-parameter-set rendering tool with no output schema, the definition covers what is produced, how large it can be, and why an agent would want it. The remaining gap is minor: it never confirms the image is returned inline versus as a path/URL, which matters for a binary-producing tool.

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 0%, so the description must carry the load; it does well for scale (range 0.5–3, default 1.5, and the resolution cap) and conveys that page is a single page number. It adds nothing about paper_id's required format (^p[0-9a-f]{16}$) or that page numbering is 1-based, leaving two of three parameters partially or wholly undocumented.

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 (render) and resource (ONE page) plus the output artifact (PNG image), so an agent knows exactly what it produces. The emphasis on 'ONE' implicitly contrasts with the multi-page sibling read_paper_pages, and the parenthetical use cases ground the tool concretely.

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 parenthetical use cases (checking formulas, tables, figures, two-column reading order) give clear situational context for selecting this tool over text-extraction siblings. It stops short of naming an explicit alternative or stating when not to use it, so it falls just below the top tier.

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