extract_api_data

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

With no annotations, the description must disclose behavioral traits. It mentions navigation and returning parsed JSON, but fails to clarify side effects such as tab behavior, whether the current page is replaced, filtering behavior of apiPattern, or how waitForSelector affects capture. This leaves significant uncertainty for a network-capturing tool.

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?

The description is two short sentences with no filler. It front-loads the core action ('Navigate to URL and capture all API/XHR responses') and adds a concise outcome ('Returns parsed JSON data').

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?

Given 6 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return structure, filtering behavior, timeouts, or how parameters interact. The tool appears more complex than the description supports, leaving the agent to infer key operational details.

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. The description adds minimal meaning beyond the schema—it implies capturing API/XHR responses aligns with apiPattern but does not explain extractFields or waitForSelector. No additional value is provided over the 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 the tool navigates to a URL and captures API/XHR responses, returning parsed JSON data. This is a specific verb+resource combination, but it does not explicitly differentiate from sibling tools like capture_network_on_action or navigate_and_extract_content.

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?

No guidance is provided on when to use this tool versus alternatives such as capture_network_on_action or intercept_and_modify_traffic. The description only states what it does, not when it should be preferred.

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