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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one important trait: the result is a temporary download URL valid ~2 days. However, it says nothing about credit consumption (only the `sandbox` schema field hints at credits), authentication, rate limits, or whether failures still consume credits.

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 sentences, zero waste, with the conversion capability front-loaded and the return value immediately after. Nothing could be removed without losing 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?

For an eight-parameter, mutation-free but credit-bearing tool with no annotations and no output schema, the description covers purpose and the return artifact well. It leaves the cost model and the sandbox-versus-paid decision unexplained, which is a meaningful gap an agent would need when choosing call settings.

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 every one of the eight parameters is already documented, including the format enum and the sandbox/credit tradeoff. The description merely repeats the format list, adding no new meaning such as default behavior or interactions between `wait_for`, `delay`, and `css`; baseline 3 applies.

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 specific verb ('Convert') and both the accepted inputs (HTML document or URL) and all four output formats, so the agent knows exactly what the tool produces. It stops short of naming siblings only because none of them overlap (create_template, list_logs, pricing, etc.), so the tool is still unambiguously identifiable.

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?

No guidance on when to prefer this over alternatives, when to use a URL versus raw HTML, or when the sandbox mode is appropriate. The agent must infer everything from the schema property descriptions rather than from the description itself.

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