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

Beyond the annotations, the description discloses default return format (rendered HTML without asset inlining), the runtimeConfig alternative returning extracted data, managed proxy selection, bounded blocked-page retries, and opt-in residential escalation. That is substantive behavior not encoded in the annotations, though permissions, rate limits, and latency/cost tradeoffs of proxy pools are unstated.

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?

Content is front-loaded with purpose, then usage, then return semantics, and nearly every sentence carries information. The alias-equivalence sentence is somewhat mechanical given each parameter schema already states the alias, but overall the density is justified.

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 9-parameter, nested-object tool with no output schema, the description covers the two possible return modes, the failure signature of empty extractions, retry and proxy behavior, and the recommended follow-up tool. An agent can invoke it correctly without opening the schema.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema does not: the alias equivalence between snake_case and camelCase forms, the role of wait_for_selector as a render-readiness gate, and the constraint that runtimeConfig must match the rendered page. runtimeConfig remains opaque (additionalProperties true) and is only loosely characterized.

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?

Description uses a specific verb+resource ("navigates to a URL, waits for it to render, and returns the page content") and differentiates from raw HTTP fetch and from importio_get_html. It does not explicitly position itself against close siblings like importio_render, importio_goto, or importio_action_render, which keeps it short of a 5.

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?

It gives explicit routing: use wait_for_selector when an element must exist, call this first for unknown data pages, then inspect HTML via importio_get_html with options.replaceAssets=false. It also provides a diagnostic rule for empty extraction results, so the agent knows both when to use it and how to interpret failure.

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