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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core conversion behavior but says nothing about whether the tool fetches the page itself, whether the input should be a URL or raw HTML, rate limits, size constraints, or failure modes. This leaves the tool's operational behavior largely opaque.

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 sentence with no filler and states the core function immediately. The 'Web2md:' prefix is mildly redundant with the tool name, but overall it is efficiently sized and front-loaded.

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 tool with no output schema and no annotations, the description is the only information source, yet it fails to specify the input format, potential limitations, or expected output shape. The central ambiguity—whether the agent should pass a URL or HTML markup—makes this incomplete for reliable invocation.

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?

Although schema coverage is 100%, the parameter description 'Input to process' is tautological and provides zero semantic value. The tool description hints that 'input' is a web page (implying a URL), but it never explicitly confirms the expected format, leaving ambiguity between a URL and HTML content—especially critical given the x402-html-to-markdown sibling exists.

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 states a clear verb and resource: 'Convert a web page to Markdown.' This is specific enough for an agent to grasp the core function. However, it does not distinguish itself from close siblings like x402-html-to-markdown, x402-web-scrape, or x402-web-retrieve, so it misses the top score.

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 gives no guidance on when to use this tool versus alternatives. Given the large sibling set containing x402-html-to-markdown, x402-web-scrape, x402-web-retrieve, and x402-fetch, an agent cannot determine whether to call this tool or its neighbors without additional context.

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