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

With no annotations provided, the description carries the full burden of disclosure. It clearly explains that the tool runs JavaScript and returns the final DOM as HTML text, which is important behavioral context. It does not mention timeouts, failure modes, or resource cost, but the core behavior is transparent.

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 well-structured sentences with no wasted words. The key differentiator, JavaScript execution and final DOM, is front-loaded, followed by concrete use cases and return type.

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 simple three-parameter tool with no annotations and no output schema, the description gives enough context about when to use it and what it returns. It could mention limitations or failure behavior, but an agent can correctly select and invoke the tool based on the information provided.

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 a useful description in the schema. The main description does not add parameter-level details, so the baseline score of 3 is appropriate.

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 and resource: fetch a page's HTML after JavaScript has executed. The emphasis on executing JS and returning the final DOM clearly distinguishes it from the sibling tools screenshot_url and url_to_pdf, which produce visual or PDF output rather than HTML text.

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?

Provides explicit usage context: use when a plain HTTP fetch returns an empty shell or loading spinner, especially for single-page apps or client-side rendered sites. It does not explicitly mention when not to use it or name the sibling tools, but the conditions are clear enough.

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