markdown-extractor

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

With no annotations, the description carries the full burden, and it does well: it discloses the paid nature, the x402 v2 protocol, the Base Mainnet network, the exact cost of 0.01 USDC per call, and automatic payment from BASE_PRIVATE_KEY. It also points to external API documentation for request body details. It could add failure behaviors or rate limits, but the key side effect—charging money—is explicitly stated.

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 three sentences and information-dense. The core action is front-loaded, followed by the payment/authentication model, then the pointer to detailed request fields. No sentence is filler; the only minor issue is some jargon ('x402 v2 protocol', 'eip155:8453') that may be opaque to some agents but is still precise.

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 empty schema, no annotations, and no output schema, the description covers the essentials: what it does, cost, network, payment source, and where to find request body details. It could be more complete by stating the exact URL field name or response format, but the external OpenAPI link reduces that gap. It is strong but not flawless.

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?

The input schema is effectively open with additionalProperties true and zero declared parameters, so the description must compensate. It does not enumerate fields, but it identifies the core input by saying the tool 'fetches a public URL' and directs agents to the OpenAPI spec for tool-specific request body fields. This adds meaning beyond the empty schema, though it relies on an external URL rather than being fully self-contained.

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 opens with a specific verb and resource: 'Fetches a public URL and returns clean, token-efficient markdown.' This clearly distinguishes it from sibling tools like spa-dom-to-md or svg-bar-chart-renderer by emphasizing URL fetching and markdown conversion. Even without naming siblings, the core function is unmistakable.

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 clear usage context: it is 'designed for autonomous AI agents to call directly,' requires no API key or signup, and is restricted to public URLs. It explains the payment model and cost, which is essential for deciding when to use it. It does not explicitly contrast it with sibling tools, so it stops short of full alternative-based guidance.

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