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

Annotations only cover safety flags (readOnly/openWorld/idempotent/destructive), so the description carries real weight and delivers: the fetch ladder (plain http first, browser only when needed or render_js is 'always'), credit cost 1-4 plus +1 for screenshots, the 12,000-char caps, and that browser actions run before the read. What it omits is failure/timeout behavior and auth requirements, but coverage is well above the annotation floor.

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?

Front-loaded with the return payload before the routing guidance, and every clause carries information (cap sizes, cost, ladder). The actions enumeration is dense but relevant; it is long without being padded.

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 describing the return shape in detail, and it supplies the cost, fallback, and browser-action behavior an agent needs to call correctly against a large sibling set.

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 coverage is 100%, so the baseline is 3, but the description adds genuine semantic detail: it explains render_js 'always', the actions vocabulary (click, type, select, press, wait, scroll, 'until_gone', each), and that a parse_documents key in config overrides the top-level flag.

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+resource ('Fetch one URL ... return the whole page') and enumerates exactly what comes back (config formats, raw html capped at 12,000 chars, head, extracted fields, images, engine; no link list). It distinguishes itself from scrape_urls and get_page by name.

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?

Gives explicit when-to-use ('a single page that needs browser steps, structured fields or a settings trial before create_project') and routes two alternatives with their selecting conditions: scrape_urls for plain content of known URLs, get_page for an already-stored page without fetching.

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