scrape

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'source-aware routing' but does not explain what that entails, nor does it disclose any side effects, authentication requirements, rate limits, or potential destructive actions.

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 11-word sentence that efficiently conveys the core purpose and unique feature. While concise, it sacrifices necessary detail, but the sentence earns its place by being direct and front-loaded.

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 presence of two parameters with no schema descriptions, a potentially complex 'source-aware routing' behavior, and no annotations, the description is insufficiently complete. It fails to clarify key aspects like how to use 'kwargs' or what the 'source-aware routing' implies, even though an output schema exists.

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 description coverage is 0%, and the description does not add any meaning for the two parameters. 'url' is implicitly understood, but 'kwargs' is left completely unexplained, making it non-trivial for an AI agent to determine correct values.

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 action ('Scrape a URL') and a distinguishing feature ('source-aware routing') and outcome ('return structured content'). It is specific enough to convey the core purpose, though it does not explicitly differentiate from sibling tools like 'fetch' or 'extract'.

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 provided on when to use this tool versus alternatives. There is no mention of when not to use it, prerequisites, or comparisons with sibling tools like 'fetch', 'search_free', or 'crawl'.

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