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

Annotations already cover read-only and open-world behavior, and the description adds meaningful context beyond them: type-checking, null/missing semantics, the returned shape, billing at 10 credits per successful call, and rejection before billing for schema mismatches. It stops short of rate limits or auth details, but the billing and rejection behavior are substantive disclosures.

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 front-loaded with the core action, then return shape, then billing. It is dense but every sentence carries useful information; the only mild weakness is that the pricing sentence is slightly tacked 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?

There is no output schema, so the description carries the burden of explaining return values, and it does so with the exact keys { url, finalUrl, title, data, missing }. Combined with the full parameter schema and annotations, it is complete enough to call correctly, though it omits guidance about dynamic pages or partial extraction behavior.

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 100%, so the URL and schema parameters are already fully documented. The description only restates the 20-field cap and adds a high-level note that input must match the schema, which adds little beyond the schema itself.

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?

States a specific verb and resource: it scrapes a public page and fills a flat typed schema. This clearly distinguishes it from generic scrapers, but it does not explicitly name or differentiate from close siblings such as web-scrape or page-markdown.

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 implies the use case (extract typed fields from a page) but gives no explicit when-to-use guidance, no when-not-to-use guidance, and does not route the agent to alternatives like web-scrape, page-markdown, or web-contents.

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