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

With no annotations, the description carries the burden and discloses key behavior: paid cost, x402/Base network, MCP returns payment requirements, and settlement requires a separate POST with payment headers. It omits some post-settlement return details, but the most important operational behavior is exposed.

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 compact and front-loads the paid cost before stating the purpose and payment flow. It is dense and telegraphic but every sentence carries relevant operational information.

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?

Given no annotations and no output schema, the description explains the payment-requirements behavior and settlement endpoint, which is essential. It still leaves some gaps around what the tool returns after successful settlement and how payment failures are surfaced.

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, but it only says "URL" without specifying constraints, examples, or expected URL types. The single parameter is simple and the schema has format uri, but the description adds little meaning beyond that.

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 makes the core purpose clear: it converts a URL into clean markdown, and the tool name reinforces the verb-resource pairing. It does not explicitly distinguish this from sibling tools such as extract_structured, but the purpose itself is understandable.

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 explains the payment workflow: the MCP call returns payment requirements, and settlement happens via POST /v1/scrape/markdown with x402 headers. However, it does not say when to use this tool instead of siblings like check_url or extract_structured.

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