web-scraper

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

No annotations are provided, and the description gives zero behavioral information. It does not mention side effects, navigation behavior, or anything that happens when the tool runs.

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 text is extremely short, but this is under-specification rather than purposeful conciseness. There is no meaningful sentence or structure that helps an agent act.

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 four parameters and no output schema, the description is completely inadequate. It provides nothing about inputs, behavior, return values, or how it differs from sibling tools.

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 explain any of the four parameters (url, waitMs, actions, fullPage). The agent is left to guess their meanings and formats entirely.

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 'V1 Browse' simply restates the tool name with a version identifier. It contains no verb, no resource specification, and no explanation of what the tool does, so an agent cannot infer its purpose.

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?

There is no guidance on when to use this tool versus the siblings fetch, web_crawl, or captcha_solve. The description provides no context whatsoever about appropriate invocation conditions.

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

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, and it discloses nothing. It does not mention network calls, external solving services, side effects, blocking behavior, failure modes, or return semantics. The agent is completely blind to what happens when the tool is invoked.

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 text is short, but this is under-specification rather than conciseness — a single vague phrase that merely restates the tool name. The available space is wasted, and there is no structure or front-loaded information to speak of.

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?

The tool has three undocumented parameters, no annotations, and no output schema, making the description the sole source of guidance — and it provides none. An agent cannot determine input requirements, expected output, or how this tool relates to browse, fetch, and web_crawl. The definition is wholly inadequate for correct selection and invocation.

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 adds zero meaning to url, siteKey, or captchaType. Although the parameter names hint at a CAPTCHA service integration, the description does not explain expected formats, which combinations are required, or what captchaType values are valid. The description fails to compensate for the low schema coverage.

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 'V1 Captcha Solve' is essentially the tool name restated with a 'V1' prefix — a near-tautology. It does not specify what solving entails, what resource is operated on, or what output is produced. An agent can only infer the vague purpose of solving a CAPTCHA, with no differentiation from its siblings.

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 offers zero guidance on when to use captcha_solve versus fetch, browse, or web_crawl. There is no mention of triggering conditions (e.g., encountering a CAPTCHA during browsing), prerequisites, or alternatives. An agent has no basis for selecting this tool.

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

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it discloses nothing: no indication of network effects, side effects, error behavior, rate limits, or return data. The version tag provides zero behavioral transparency.

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 text is short, but this is under-specification rather than conciseness. "V1 Fetch" contains no useful content that an agent can act on.

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?

A network-related tool with two parameters, no annotations, no output schema, and no parameter descriptions is completely underspecified. The agent cannot determine what fetching means, what the return value looks like, or how timeouts behave.

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 compensate by explaining url or maxTimeout. Even though the parameter names hint at meaning, units, defaults, requiredness, and semantics of maxTimeout are undocumented.

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?

"V1 Fetch" merely restates the tool name with a version label and does not state what the tool does, what resource it acts on, or how it differs from siblings like browse and web_crawl. There is no verb-object structure or functional content.

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 no guidance on when to use fetch versus browse or web_crawl. No context, exclusions, or alternative selection criteria are given.

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

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

With no annotations provided, the description carries the full burden of disclosing behavior, but "V1 Web Crawl" says nothing about crawling semantics, pagination, following links, limits, timeout behavior, authentication, or side effects. An agent has no way to predict what invoking this tool will do.

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 text is short, but this is under-specification rather than effective conciseness. The single phrase provides no useful information and is not structured to help an agent decide whether to invoke the tool.

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 three undocumented parameters, no annotations, and no output schema, the description is grossly incomplete. It omits what a crawl returns, how max_pages and maxTimeout are interpreted, and how this relates to sibling tools.

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 compensate by explaining url, max_pages, or maxTimeout. Units, optionality, and behavior of these parameters are entirely undefined.

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 "V1 Web Crawl" merely restates the tool name web_crawl with a version prefix; it does not state a specific verb, output, or scope. It also fails to differentiate from sibling tools browse and fetch, which likely overlap in retrieval behavior.

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 offers no guidance on when to use web_crawl versus browse, fetch, or captcha_solve. There is no mention of appropriate use cases, exclusions, or alternatives, so an agent must guess from the name alone.

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