browser_batch_extract

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

Annotations already indicate a write operation (readOnly=false). The description adds context by specifying the data is stored in a ZeroDB table and mentions the credit cost per URL. It discloses the main side effect (writing rows) and a cost metric, which is valuable beyond the annotations. Minor gaps remain (e.g., failure behavior), but it is not contradictory.

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 sentences, front-loaded with the core action and purpose, and includes the cost in a compact parenthetical. Every sentence earns its place with no redundant information.

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?

The tool involves multiple URLs, storage to a table, and has no output schema. The description covers the core workflow, cost, and usage context. It does not describe return values or error semantics, but for a batch extraction-to-table tool this may be less critical. Overall, it is sufficiently complete for a 4-parameter tool with 100% schema coverage.

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 all parameters are documented in the schema. The description restates the URL limit ('up to 10 URLs' matching maxItems) and mentions 'store rows' for table_name, but adds no new semantic detail beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb 'Extract' with a clear resource ('structured data from up to 10 URLs') and a destination ('store rows in a ZeroDB table'). It differentiates from siblings by emphasizing the batch capability ('up to 10 URLs in a single call') and naming 'multiple pages at once.'

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 description provides an explicit usage condition: 'Use when you need to scrape multiple pages at once.' This gives clear context, though it does not explicitly name alternatives or exclusions. It effectively tells the agent when this tool is appropriate.

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