extract_structured

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It fails to mention key behaviors such as whether JavaScript rendering is used (though a parameter exists), rate limits, authentication needs, or data retention policies. The description only covers core functionality.

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 long, front-loaded with the action and resource, provides a clear usage example, and contains no superfluous words. Every sentence serves a purpose.

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?

While the description explains the tool's niche among siblings (structured vs. general scraping), it omits details about the output format (likely a dict of field names to values) and does not mention the javascript parameter's impact. Overall, it covers the essential context but has minor gaps.

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 already documents all three parameters (url, fields, javascript) with descriptions. The tool description restates the concept of CSS selectors but adds no additional meaning beyond the schema. Given high schema coverage (67%+), a baseline of 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 clearly states the verb 'scrape' and resource 'URL', specifies extracting fields with CSS selectors, and distinguishes from sibling tools by focusing on structured data from known page layouts, with concrete examples (product price, article title).

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 a usage hint ('Use when you need structured data from a known page layout') but lacks explicit when-not-to-use guidance or alternatives like scrape_url for unstructured extraction or scrape_multiple for multiple pages.

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