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

Annotations already cover safety (readOnly, non-destructive, open-world). The description earns credit beyond that by disclosing the external ScrapeUnblocker API dependency, the structured non-HTML return format with a ready-to-use selector per element, and the render-wait capability implied by wait params. It does not mention cost, rate limits, or failure behavior, which keeps it from a 5.

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, both dense and front-loaded: the return shape and element enumeration come first, the routing guidance second. No filler or restated title text.

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 specifying the JSON envelope and element contents, and it also states the downstream workflow. Error handling and pagination/limits on large pages are the only notable omissions for a 5-parameter open-world fetch tool.

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 the schema already documents every parameter including wait_method/wait_value pairing and the ISO country code. The description adds no syntax or constraint detail beyond what the schema provides, so the 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 and resource (fetch a page, return its interactive elements), enumerates the element types, and pins down the exact return shape ({url, count, elements:[...]}) while explicitly contrasting it with raw HTML, which distinguishes it from fetch_html/fetch_markdown. An agent can pick it over every sibling without opening a 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?

Gives a concrete workflow: discover targets here, then drive the page with browse_page's `steps` param, naming the sibling explicitly. It lacks an explicit when-not (e.g., use fetch_markdown when you want text content), so a small inference remains.

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