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

The description discloses several non-obvious behaviors beyond the annotations: it makes external provider calls, records billable usage, enforces account limits, and may fall back to another eligible provider. This is valuable context that annotations alone do not convey, and it does not contradict the annotation flags.

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 compact and front-loads the core purpose in the first sentence, followed by a usage condition and behavioral warnings. The phrase 'Execute, scrape, or extract content' is slightly redundant, but overall the description is efficient and well-organized.

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?

While the high-level behavior is clear, the tool has six parameters, no output schema, and critical extraction-quality controls that the description does not address. An agent would not know how to set markers, quality thresholds, or character minimums correctly, or what a successful result looks like. This is a significant completeness gap for a non-trivial tool.

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 only 33%, with url and requiredMarkers documented, but minQuality, minCharacters, optionalMarkers, and minRequiredMarkerRatio lack schema descriptions. The tool description does not explain these parameters, their defaults, or how markers and quality thresholds affect extraction, so it fails to compensate for the coverage gap.

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 identifies the operation: executing, scraping, or extracting content from a URL via a connected web-extraction provider. This sufficiently distinguishes it from sibling tools like billing_status, quote, and recommend, which handle unrelated billing and recommendation tasks.

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 explicitly states the primary usage condition: 'Use only after the user explicitly asks to run the extraction.' It also warns about external provider calls and billable usage. It does not name alternative extraction tools, but no such sibling is present, so the guidance is clear and practical.

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