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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the color coding of the overlay (red=unfilled, green=filled), that field numbers are f-numbers, and that the inspection step records this visual confirmation.

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 resource is stated first, then each flag is introduced with its effect and intent, and there is little wasted text. The multi-line formatting is dense but front-loaded and each sentence carries information.

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?

With no output schema, the description does convey that the return is a page image, and readOnlyHint covers safety. But for a 6-parameter tool with 0% schema coverage, leaving page, form_id, and values undocumented and offering no differentiation from inspect_form makes it only adequately complete.

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, and it does for three of six parameters: boxes (overlay semantics and colors), region (format [left,top,right,bottom] in pt and the zoom purpose), and grid (50pt spacing and why). It leaves page, form_id, and values completely unexplained, so it only partly compensates for the coverage gap.

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 names a specific verb+resource: it renders the page image of a PDF form, with optional overlays. It is clear what the tool returns, but it makes no attempt to distinguish itself from the sibling inspect_form, which an agent would plausibly confuse it with.

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 gives useful mode-level guidance (use boxes=true to see field frames and numbers, grid=true when correcting positions, boxes=false after filling to verify against the submission). However, it never says when to use view_form versus inspect_form or the other form siblings, so the routing decision is left implicit.

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