visit

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

With no annotations, the description carries full burden. It discloses Chromium usage, rendering behavior, performance notes (e.g., screenshot adds ~200ms), and return structure. Minor gap: no mention of idempotency or side effects, but it's clear this is a read-only operation.

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?

Well-structured with a concise purpose statement, bullet-style parameter list, and return documentation. Slightly verbose in parameter descriptions but overall efficient and front-loaded.

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?

Covers all parameters, explains returns, and provides context for use relative to siblings. No mention of rate limits or concurrency, but given the output schema and detailed parameter docs, it is sufficiently complete for effective tool use.

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?

Despite 0% schema coverage, the description provides detailed explanations for all 7 parameters, including semantics, defaults, and usage examples (e.g., 'wait_for_selector: Optional CSS selector to await before reading the DOM'). Fully compensates for missing schema descriptions.

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 'Open a URL with a real Chromium and return its rendered state' and distinguishes from cheaper fetch tools, citing specific use cases like SPAs, JS-rendered charts, and login-walled pages.

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?

Explicitly says 'Use when the cheaper fetch tools fail' and lists alternative tools (web_fetch, pdf_fetch, http_post_form) with concrete scenarios, providing excellent when-to-use guidance.

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