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

The description adds valuable behavior beyond the annotations by disclosing a hard cost ('1 credit per call') and a temporary 15-minute download link. It also translates `scale` into DPI values, which is useful operational context not captured by the schema or annotations.

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?

Four short sentences, each earning its place: purpose, page/scale behavior, cost, and return artifact. Key details are front-loaded, and there is no redundant restating of schema fields.

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 tool with no output schema, the description adequately explains the return artifact and its expiry. A minor gap is that it does not clarify whether rendering multiple pages produces one link or multiple links, which could affect how an agent consumes the result.

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 baseline is 3. The description adds meaning by explaining the `scale` parameter in terms of DPI (1 = 72 dpi, 2 = 144 dpi) and clarifying that `pages` overrides the all-pages default.

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 ('Renders') and resource ('PDF pages') with output format PNG, and clarifies the optional `pages` scope. This makes it immediately distinguishable from siblings like `images_to_pdf` and `html_to_image`.

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?

Usage is implied by the title and operation: an agent can infer this is the tool to use when PDF pages need to become PNG images. However, it does not explicitly state when to prefer this over alternatives such as `screenshot_url` or `html_to_image`, nor provide exclusion conditions.

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