browser_extract_to_table

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, so the description adds the cost factor '(100 credits)' and emphasizes that data is stored directly. However, it does not disclose whether the table must pre-exist, whether rows are appended or replaced, or any potential side effects beyond storing. The cost disclosure adds some value, but more behavioral detail would improve transparency.

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 concise sentences plus a parenthetical cost note, with no redundant information. It front-loads the core action and then states the intended use case, making it easy to parse quickly.

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 has four required parameters and no output schema, and the description covers its purpose and use case succinctly. It does not explain the return value or error scenarios, but for a simple persistence tool, the given information is largely sufficient. The inclusion of cost and persist-for-later-analysis adds useful context.

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?

The input schema covers all four parameters with descriptions, and the tool description does not add extra meaning beyond what the schema already provides. Since schema coverage is 100%, the baseline of 3 is appropriate; the description's mention of 'extract structured data' aligns with the parameters but does not elaborate further.

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 extracts structured data from a web page and stores it in a ZeroDB NoSQL table, distinguishing it from sibling tools like browser_extract that likely only extract without persisting. The verb 'extract' and resource 'web page' plus the specific outcome 'store it directly in a ZeroDB NoSQL table' provide a precise purpose.

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 explicitly says 'Use when you need to scrape data and persist it for later querying or analysis,' providing a clear context for when to invoke this tool. It does not mention alternatives or when not to use it, but the use case is specific enough to differentiate from siblings like browser_extract.

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