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

With no annotations, the description carries the transparency burden. It clearly discloses the paid nature, the two-step payment mechanism, and the output format (PNG screenshot via headless browser). While it doesn't discuss error handling or timeout behaviors, the key behavioral traits (cost, render method, output) are stated.

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?

Two tightly structured sentences: the first covers core function, the second covers payment specifics. Every word earns its place, and the critical payment flow is front-loaded after the main purpose. No redundancy or fluff.

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?

The tool is simple and the description covers the essential facts: headless browser rendering, PNG output, size configurability, and payment requirements. With no output schema, stating the return type is sufficient. The description doesn't explain error conditions or broader use cases, but for a screenshot tool this is adequate.

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 100%, so baseline is 3. The description adds value beyond the schema by explaining the two-step x_payment workflow ('call without x_payment to receive exact terms... sign them... call again'), which helps the agent sequence calls correctly. This supplemental guidance pushes it above baseline.

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 starts with 'Render a URL in a headless browser and return a PNG screenshot', a specific verb+resource combination that clearly identifies the tool's function. This distinguishes it from siblings like read_url or image_to_text, which serve text extraction rather than visual capture.

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 description provides explicit usage guidance for the payment flow (call without x_payment, sign, then call with x_payment) and points to the `pricing` tool as an alternative for viewing all prices at once. It lacks explicit 'when not to use' caveats but gives clear operational context.

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