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

Beyond the annotations, the description discloses that JS execution and network fetches are disabled, that only the submitted HTML is used, that output is retained for 24 hours, and that the response carries storage_id and storage_url. It also clarifies there is no API key or account requirement, which resolves practical auth questions the annotations do not address, and its 'stored file' framing is consistent with readOnlyHint=false and idempotentHint=false.

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?

Structure is front-loaded: purpose, then the sandbox constraint, then options, then storage lifecycle. The page-size and margin enumerations duplicate the schema and the 'No API key, no account and no sign up' clause is marketing-flavored, but both are short and the remaining sentences each carry real information.

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 no output schema, the description compensates by explaining the return shape (storage_id and storage_url) and the 24-hour retention window plus the retrieval tool. For a two-parameter tool with a nested options object, nothing an agent needs to invoke it correctly or handle the result is missing.

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 both parameters are already documented in the schema, including the same page-size, orientation, and margin values. The description restates those option values and adds only the '10mm'-style margin format example, which the schema also contains, so it adds little meaning beyond the structured fields.

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 first sentence states a specific verb and resource ('Render HTML to a PDF') and immediately scopes it with the sandbox constraint (JavaScript and network off), which separates it from the nearby html_markdown_convert sibling. An agent can tell exactly what output format it gets and what input limitations apply without opening the schema.

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 gives clear context for when this tool is applicable: HTML must be self-contained with inline data URLs because scripts and network access are disabled, and it names read_stored_file as the follow-up for retrieving the result. What is missing is an explicit exclusion or comparison, e.g. when to choose this over html_markdown_convert or store_file.

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