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

With no annotations, the description carries the full burden and does so: it discloses that Korean fonts are included, that bad input or the daily cap is refused before payment, and that the call costs $0.01 USDC via x402 on Base or Solana. It also states the exact output shape (JSON fileBase64 to decode, bytes, viewport), which is essential for a paid tool with no output schema.

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?

Dense and front-loaded: purpose first, then input contract, output shape, failure behavior, example, and price. Every clause earns its place, though the telegraphic 'Input: GET ?url=, or POST JSON {...}' phrasing is terse to the point of being slightly cryptic.

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 paid, multi-mode rendering tool with no output schema and no annotations, the description covers invocation modes, output decoding, pricing, and pre-payment validation — everything an agent needs to call it correctly and anticipate cost or refusal.

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, but the description adds real value beyond it: the width range 320-1920 (schema only gives the default), the GET-vs-POST usage split, and the meaning of full_page. Minor gap: 'full_page' is typed as a string in schema while the description writes it as a boolean-ish flag.

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 precise verb+resource: converting the agent's own HTML/Markdown or a URL into a PNG, with named use cases (social card, chart, table snapshot, preview). It does not explicitly contrast with close siblings like render_pdf or web_screenshot, so differentiation is left to inference.

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 opening 'Use when an agent must turn its own HTML or Markdown into an image... or capture a page as PNG' gives a clear triggering context. There are no explicit exclusions or named alternatives (e.g., when to prefer render_pdf or web_screenshot), so it falls short of a 5.

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