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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals the output format and price, but does not mention whether JavaScript is executed, what URL schemes are accepted, failure behavior, rate limits, or access restrictions. This is insufficient for a scraping tool with an ambiguous sibling.

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 a single sentence with no filler; the core action, output format, and cost are front-loaded. It is appropriately terse for a tool with only one parameter, though the brevity sacrifices needed guidance.

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 tool with no output schema and no annotations, the description is too sparse to be self-sufficient. It omits the exact return shape, URL requirements, and when to prefer this over browser_scraper, so an agent lacks enough context to invoke it reliably in ambiguous situations.

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 has one 'url' parameter with 0% description coverage, and the tool description does not explain accepted URL formats or constraints. The property name and 'web pages' phrasing imply an HTTP URL, but no additional semantics are provided beyond the schema.

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 states a specific action ('scrapes') and a concrete output ('clean markdown'), so an agent understands roughly what the tool produces. However, it does not distinguish itself from the sibling 'browser_scraper', which likely has overlapping functionality, so full differentiation is missing.

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?

No guidance is given for when to choose this tool over browser_scraper, render_screenshot, or pdf_extractor. The description provides no explicit conditions, exclusions, or alternative recommendations, leaving the agent to guess based on the tool name alone.

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