scrape_url

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

Without annotations, the description carries full burden. It discloses automatic detection of JavaScript rendering needs, which is a key behavioral trait. It also implies the tool fetches and returns structured data, but does not mention potential issues like robots.txt or rate limits. Overall, the transparency is good but not exhaustive.

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: the first defines the tool's function and output, the second gives a usage guideline. No unnecessary words, perfectly front-loaded. Every sentence earns its place.

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 the complexity of 9 parameters and no output schema, the description covers the main output (text, links, images, metadata) and key behaviors. It does not explicitly describe the return format or pagination, but for a scraping tool this is acceptable. Lacks mention of error handling or constraints.

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% with detailed descriptions for each parameter. The tool description adds overarching context (e.g., automatic JavaScript detection) but does not provide additional semantic meaning beyond what the schema already offers. 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 clearly states the tool scrapes any public URL and returns structured data including text, links, images, and metadata. It uses a specific verb ('scrape') and resource ('URL'), and the mention of returning structured data distinguishes it from siblings like take_screenshot or scrape_multiple.

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 provides usage context: 'Use this when you need to read the content of a webpage.' It does not, however, specify when not to use it or mention alternatives like scrape_multiple for multiple URLs, which limits differentiation.

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