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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral detail beyond its purpose; notably, the pay-to-use behavior expressed through paymentProof and the 402 price quote is only present in the schema, not the 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 a single, front-loaded sentence with no wasted words. It conveys the essential purpose clearly and efficiently.

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 simple two-parameter tool with full schema descriptions, a specified output schema, and read-only annotations, the description is largely sufficient. The main contextual gap is the payment/402 behavior, but that is already encoded in the paymentProof parameter description, so an agent can call the tool correctly.

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 parameters are already well documented. The description adds no additional meaning about the html or paymentProof fields, which is acceptable at baseline but does not elevate it.

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 uses a specific verb ('Extract') and resource ('clean JSON from messy HTML'), making the tool's function immediately clear. It also differentiates itself from siblings like scrape.bypass_captcha and analysis.summarize_clean by focusing on HTML-to-JSON conversion.

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 usage ('when you have messy HTML and want JSON') but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. The schema hint 'if you already fetched the page yourself' is a partial workflow cue, but no sibling comparison or conditional routing is given.

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