extract_data

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It only mentions extraction based on JSON Schema, but doesn't disclose whether it executes JS, handles dynamic content, any rate limits, or that it's read-only. This is insufficient for a tool with no annotations.

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?

Two concise sentences, front-loaded with the core action and then the usage condition. Every word earns its place without waste.

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 description covers the primary purpose and usage scenario, and an output schema likely explains return values. However, it omits details on the 'strategy' parameter and any constraints or edge cases, leaving clear gaps in understanding for a moderately complex schema-driven tool.

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 0%, and the description only hints at the 'schema' parameter's role through 'based on JSON Schema'. The 'strategy' parameter is completely undocumented, and 'url' is only implicitly understood. The description provides minimal added meaning beyond the schema's field names.

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 web pages using JSON Schema, and provides specific examples of requested fields (price/title/date). This distinguishes it from sibling scraping tools like scrape_url or crawl_site.

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 specifies when to use the tool: when the user requests specific fields. It doesn't explicitly name alternatives or exclusions, but the context implies it's for targeted extraction vs broader scraping.

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