fetch_batch_clean_markdown

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

With no annotations, the description carries the full burden and does disclose useful behavior: concurrency, a 10-URL limit, and a per-URL USDC fee on Polygon. However, it does not explain the payment flow, what payment_tx_hash is for, failure behavior, or whether the 'single transaction' wording refers to the API call or a blockchain transaction.

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 sentences with no wasted wording. The key functional scope is stated first, followed by the cost requirement, and both statements directly help an agent decide and call the tool.

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?

The description covers the core action, limits, and pricing, but missing details about parameter formatting and the payment flow make it incomplete for reliable invocation, especially given no annotations and no sibling differentiation.

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 must compensate for both parameters. It does not explain how the urls string should be formatted (e.g., delimiter, separated list) nor what payment_tx_hash represents or how it is used, leaving a significant semantic 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 states a specific action: batch scraping and cleaning up to 10 web URLs into Markdown in a single transaction. The 'batch' and 'up to 10' language distinguishes it from the singular sibling tools.

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 use when multiple URLs need to be fetched and cleaned, and mentions concurrency and a cost model. However, it does not explicitly recommend against using this tool for single URLs or point to siblings like fetch_clean_web_content for alternative cases.

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