proof

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

Since there are no annotations, the description carries the full burden of behavioral disclosure. It describes the complex return value structure (job_id, errors, geometry, ink coverage, cost) and provides crucial context on the meaning of visual proof elements (grey vs. red/orange frames).

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 dense and long, but every sentence provides a necessary piece of information regarding input, output, or behavior, preventing it from becoming redundant.

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 complex tool lacking annotations and an output schema, the description is highly complete, covering input formats, default behaviors, and the detailed nature of the results.

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?

Given 0% schema description coverage, the description adds extreme value. It clarifies that 'html' can be either a string or a file path, and it defines the intended use case for different input formats (.html vs .pdf).

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's purpose: to render and check printable HTML/PDF. It goes beyond a simple rename to define the entire scope of the operation, including generating a proof.

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?

It provides good usage guidelines by specifying the input types (string vs. path) for HTML and offering advice on using PDF input for pages created by other tools. It also defines default behavior when printer/profile parameters are omitted.

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