page_render

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotation behavior: it 'never silently resizes' and enforces hard limits (12 MP / 6000 px / 8 MB PNG). It does not say what happens when a request exceeds those limits (error vs. clamp), which is the one remaining behavioral gap.

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 short lines, front-loaded with the core purpose, then guidance, then hard limits. Every sentence carries distinct information and none is redundant with the schema.

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, but the description states the return shape ('inline PNG plus metadata'), the size/pixel limits, and a routing recommendation, which is most of what an agent needs. The only shortfall is undefined behavior on limit violations and undocumented file/page parameters.

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 carries the burden. It meaningfully constrains dpi with a recommended 120-180 range, but says nothing about 'file' or 'page' semantics. Two of three parameters are therefore undocumented anywhere, so it only partially 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?

States a specific verb and resource ('Return full page as inline PNG plus metadata'), and explicitly contrasts itself with the sibling page_crop for the small-label case. An agent can distinguish it from page_crop and page_text without opening a 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?

Gives an explicit starting recommendation ('Start at 120-180 dpi for an overview') and names both the alternative tool and the condition that selects it ('For small labels, use page_crop'). This is when-to-use plus when-to-use-something-else, with nothing left to inference.

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