scrapepay

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

Discloses key behavioral traits: pricing model ('Charges only on successful scrape'), compliance (robots.txt enforced), and safety (SSRF-safe). With no annotations provided, these details add significant value beyond the minimal description.

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 very short and front-loaded with pricing, which is efficient. However, it omits critical parameter explanations, so the conciseness comes at the cost of completeness.

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?

With 5 parameters, no schema descriptions, and no output schema, the description is incomplete. It does not explain what the tool returns or how parameters work, leaving the agent with significant ambiguity.

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 fails to elaborate on any of the 5 parameters (url, format, selector, wait_for, timeout_ms). The agent must infer meaning from parameter names alone, which is insufficient.

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?

Clearly states 'Web extraction via Playwright', specifying verb and resource. Additional context like pricing, robots.txt enforcement, and SSRF-safety distinguishes it from sibling tools such as screenshot or web_synthesise.

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 on when to use this tool over alternatives. While it mentions charging only on success, it does not explain scenarios for choosing scrapepay over web_synthesise or screenshot.

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