Open and inspect an allowed URL

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: the request is a GET, the URL must be allowlisted, waiting happens locally, and the call can return tables and refs. This goes beyond the structured annotations without contradicting them.

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?

A single sentence front-loads the core operation (GET-open allowlisted URL), then lists the auxiliary behaviors (wait, return tables/refs). No filler or redundancy.

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 complex tool with 8 parameters, nested schemas, and no output schema, this description is far too thin. It provides no parameter semantics, no return-value shape, no guidance on wait conditions or extraction limits, and no relationship to sibling tools. An agent would need to inspect the raw JSON schema and infer a lot.

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 0% schema description coverage and 8 parameters including complex nested objects (wait, observe, extract_tables, trace, target_id), the description does almost nothing to explain parameter meaning. 'Return tables and refs' hints at extract_tables/observe but leaves wait, trace, timeout_ms, new_target, and target_id entirely unexplained.

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 states a specific action — GET-opening an allowlisted URL — and names concrete capabilities: waiting locally and optionally returning tables and refs. It gives a clear resource and outcome, though it stops short of explicitly differentiating from open_click_verify or other opening siblings.

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?

The phrase 'in one call' implies a combined open-wait-extract workflow, giving some sense of when it is appropriate. However, there is no explicit guidance about when to prefer open_url over wait_for, extract_tables, observe, or open_click_verify, nor any exclusion conditions.

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