well-002-url-to-markdown

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

Goes well past the annotations: discloses paid execution ($0.005 USDC via x402), hard caps (1 MB body, ~10s timeout, max 5 redirects), a no-storage guarantee, and a no-warranty disclaimer. Annotations only cover the read-only/idempotent/open-world profile, so this extra context is genuinely additive.

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?

Four tight sentences, front-loaded with purpose then constraints then return shape. Every sentence carries distinct information (cost, rejection rules, caps, response keys, disclaimer); no 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?

No output schema exists, so the description compensates by enumerating the returned JSON keys (url, final_url, title?, content_type, markdown, warnings) plus cost, limits, and data-handling posture. An agent has everything needed to call and interpret the result.

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?

Only one parameter at 100% schema description coverage, which already documents the accepted scheme and rejected targets. The description restates the same constraint rather than adding syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (convert) and resource (public https URL → markdown) with the exact scope qualifier 'public https'. The cost line and constraint list make the tool's identity unambiguous even without siblings to differentiate from.

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?

Gives clear operating conditions: https only, with http/file/data/localhost/private IPs explicitly excluded. That tells the agent when the call will fail, but there is no statement of when to prefer this over another approach (no alternatives exist, so this is a mild gap rather than an omission).

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