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

With readOnlyHint=true already declaring a safe read, the description still adds real behavioral value: it renders PNGs, numbers boxes in reading order, marks signature fields, and warns signature fields 'cannot be filled'. It does not discuss rate limits or exact return envelope (a list of pages plus field mappings), but the added context is substantial.

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?

Three tight sentences that front-load the render action and the numbered-box output, then explain the field-number mapping and the signature caveat. Efficient, though the closing instruction is slightly instructional filler.

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?

No output schema exists, so the description must carry the return value, and it does explain the pages-plus-field-list shape and the PNG output. It is essentially complete for an agent to call it correctly; only the exact response structure is left somewhat loose.

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 every parameter (dpi, file, async, pages, webhook_url) is already documented, and the description adds nothing about their syntax or defaults. Baseline 3 applies when the schema does the heavy lifting.

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), resource (pages of a PDF form), and concrete output (PNG images with a numbered box on every fillable field, numbered in reading order). This clearly distinguishes it from read-pdf-form (reads field data) and fill-pdf-form (writes values), so an agent can pick it without opening any schema.

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?

It positions itself as the visual precursor to fill-pdf-form by stating the numbered field names are exactly what fill-pdf-form takes, and tells the agent to open the page images to locate fields. That is clear context for when to reach for it, but there is no explicit when-not or direct naming of read-pdf-form as the data-oriented alternative.

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