fetch_clean_web_content

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

With no annotations provided, the description carries the full burden and does disclose one genuinely non-obvious behavioral trait: 'Requires 0.01 USDC on Polygon' flags an external financial cost and chain dependency. However, it omits other behavioral details like how the payment_tx_hash is produced, what happens without payment, or rate/usage limits.

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?

Two crisp, front-loaded sentences of 16 words total. The primary capability lands in the first sentence, the critical cost dependency in the second. Zero filler.

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 an output schema, much is covered, but the payment flow is a black hole: the sibling get_payment_info strongly suggests a payment-generation prerequisite that is never connected. An agent would be stuck knowing it must pay without knowing how to attach the transaction hash.

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%, so the description needed to compensate entirely, yet it never names 'url' or 'payment_tx_hash'. The '0.01 USDC on Polygon' clause loosely implies the purpose of the payment parameter, but the agent is left guessing about the transaction-hash format or how to obtain 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 verb phrase 'Fetches and transforms' paired with 'any webpage' and the output 'AI-ready clean Markdown' gives a specific verb+resource+result description. It indirectly distinguishes itself from siblings like fetch_youtube_transcript and fetch_pdf_markdown via 'any webpage,' though it never explicitly names alternatives as in the calibration high example.

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?

Usage context is only implied: 'any webpage' suggests this is the general-purpose fetcher among the sibling specializations, and the payment mention signals a real-world prerequisite. However, there are no explicit exclusions ('use fetch_youtube_transcript for videos') or references to sibling tools.

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