ExtractEdge

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

With no annotations, the description carries full behavioral disclosure burden. It explicitly states the pipeline: fetches the page, strips ads/nav/scripts, converts main content, and returns metadata (title, description, links). It also discloses the payment mechanism (x402 USDC on Base) and the demo cap, which are material behavioral constraints. It omits error/rate-limit behavior but covers the defining traits well.

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 three-sentence description is dense but free of filler; each clause covers a distinct aspect — core capability, transformation behavior, and cost/demo tradeoff. It is front-loaded with the primary purpose before details. This is an appropriately sized definition for a moderately simple 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 tool has no output schema, so the description compensates by mentioning the response content: markdown/plain text with metadata. It also covers the payment requirement and demo limit, which are central to using the tool correctly. Minor gaps like error handling and page-size limits exist, but the essential calling context is present.

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 coverage is 100%, so the schema already explains url, demo, and format. The description adds a small amount of context by framing the URL as 'public web page' and reinforcing that demo yields a capped preview, but these largely mirror the schema text. The description's mention of output metadata is behavioral, not parameter-specific, so the added semantic value is modest.

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-resource pairing: 'Extract clean markdown (or plain text) content from any public web page URL.' It further clarifies the transformation pipeline (fetch, strip ads/nav/scripts, convert main content to markdown) and names an internal implementation ('Firecrawl-lite'). This clearly distinguishes the tool from a generic fetch or HTML grabber, even though there are no siblings listed.

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 scopes input to 'any public web page URL,' implicitly excluding authenticated or private pages. It also presents a clear decision rule between the free demo mode ('limited to 3000 chars') and paid extraction (0.001 USDC/extract), telling the agent when cost applies. It doesn't explicitly state when to prefer this over alternatives, but no siblings exist to differentiate.

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