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

The description adds meaningful behavior beyond annotations: it costs 1 credit per call, returns a temporary link valid for 15 minutes, uses a real browser, and blocks private networks. These details help the agent understand side effects, constraints, and output handling.

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 description is short and well-organized into behavior, constraints, cost, and return value. It loses a point because the opening phrase largely repeats the tool title, though the remaining content earns its place.

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 all 7 parameters fully documented in the schema, the description covers the essential operational context: how the URL is loaded, cost, network restrictions, and the temporary-link return behavior. No critical gap prevents correct invocation.

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% and each parameter already has clear descriptions, ranges, defaults, and format details. The description adds only the general public-URL and network-blocking context, not new per-parameter meaning.

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 clearly states the tool loads a public URL in a real browser with JavaScript enabled and takes a screenshot. It names a specific resource ('public web page') and action, and the phrase 'public URL' distinguishes it from tools that convert local/HTML input.

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 implies usage for publicly accessible web pages by explicitly blocking private networks and internal addresses. However, it does not name alternatives like html_to_image or transform_image, nor does it state when to prefer this tool over them.

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