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

With no annotations, the description carries the full behavioral burden but only lists output artifact types. It says nothing about fetching behavior, JS rendering, rate limits, handling of non-HTML or blocked pages, or error cases, and does not state that it is a read-only operation.

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?

A single well-packed sentence, front-loaded with the verb and the highest-value content (the artifact types), with zero filler or redundancy.

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 and no annotations, so the description's enumeration of artifact types usefully doubles as a partial return-value contract. However, it omits the fallback behavior when none of those artifacts exist, the role of the optional 'html' parameter, and any error semantics, leaving real gaps.

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 schema already documents 'url' and the optional 'html' string. The description adds no parameter-level meaning, such as what happens when 'html' is provided alongside 'url' or whether 'html' overrides fetching; baseline 3 is appropriate.

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 names a specific verb (extracts) and enumerates the exact artifact types it returns (JSON-LD schemas, OpenGraph tags, HTML tables as JSON, code blocks) from a webpage URL. That is far more precise than a generic 'extract data' tool, though it never explicitly differentiates itself from siblings like distill_webpage or recon_webpage_skeleton.

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 when-to-use guidance and no mention of alternatives, despite several sibling tools that also process webpages (distill_webpage, recon_webpage_skeleton, extract_ecommerce_catalog). The description also gives no hint about when to supply the optional 'html' parameter versus letting the tool fetch the URL.

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