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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool outputs markdown plus structured metadata (title, headings, links, word count), is keyless, costs $0.03 per call, and is limited to a single page per call. It does not mention error handling or rate limits, but for a simple scraping tool, it covers the key behavioral aspects.

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 front-loaded with the main purpose and includes essential details (cost, parameters, example) in a compact format. It is informative without being verbose, and the structure flows logically from purpose to constraints to parameters. It could be slightly more concise, but it earns its length.

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 single-URL scraper with a weak schema and no output schema, the description covers the necessary context: what it does, what it returns, its constraints (single page, no key), cost, and parameter semantics. It doesn't discuss error handling or edge cases, but these are not critical for a simple tool. An agent has enough information to invoke it correctly.

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 is minimal (a generic 'params' object with arbitrary properties) and schema description coverage is 0%, so the description must compensate. It does so by explicitly naming 'url' and 'maxChars' with brief explanations ('page URL to scrape', 'markdown cap') and provides an example. This adds meaning beyond the schema, though it doesn't elaborate on optional constraints or defaults.

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's purpose: scraping a single web page to clean markdown. It names the specific verb ('Scrape') and resource ('any web page'), and differentiates itself from siblings by highlighting it is a single-page scraper, not a site crawler, and a per-call alternative to Firecrawl. This is specific and distinguishes it from other tools like serp or domain_info.

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 clear context for when to use the tool: for reading a page without a browser, with no API key, and as a per-call alternative to Firecrawl. It explicitly states 'Single page per call, not a site crawler,' which excludes crawling use cases. While it doesn't explicitly list when not to use it beyond that, the context is sufficient for an agent to decide.

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