webscrape.scrape

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it performs a static HTML fetch and does not execute JavaScript, which is a key limitation. This enriches the agent's understanding of what the tool actually does.

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 sentences with no filler. The first sentence states purpose and outputs; the second adds a critical limitation. Information is front-loaded and every word 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?

For a simple one-parameter read tool with an output schema, the description is complete: it covers what the tool does, what it returns (title, headings, links, images, text), and its key limitation. No missing behavior or parameter info is needed beyond the schema.

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% for the single 'url' parameter, giving a baseline of 3. The description adds meaning by stating the URL will be fetched as static HTML, implying it should be a direct page URL rather than a JS-driven app. This is a meaningful constraint beyond the schema's simple 'The URL to scrape'.

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?

Description clearly states the verb 'Scrape' and resource 'webpage', and enumerates the extracted structure: 'title, headings, links, images, and text content'. It also adds a distinguishing limitation ('static HTML fetch') that separates it from sibling tools like webscrape.extractDesign.

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 gives clear context for when to use the tool: for static HTML pages, explicitly noting '(does not render JavaScript)'. This implies when not to use it (JS-heavy sites) but does not name an alternative tool, so it falls short of an explicit when-not/alternatives statement.

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