MCPFax Web Extract

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

With no annotations available, the description carries the burden of explaining behavior. It usefully discloses the ordering ('most-requested first'), the aggregate nature of the data, and that it includes categories where nothing available yet serves. However, it does not clarify whether this is a read-only operation or describe any properties of the returned data beyond the ordering and category scope.

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 short, but the first sentence is a fragment and the final phrase 'with the categories nothing available yet serves' is grammatically awkward and harder to parse than it should be. The 'FREE, no payment' opener is somewhat redundant with the title's 'free' suffix. Still, most sentences add some value and length is appropriate.

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 single-optional-parameter report tool, the description covers the main subject and ordering but leaves the returned value's shape unspecified. Since there is no output schema, another sentence explaining what fields or list items appear would help an agent know what to expect. The description is sufficient for a basic call but not rich enough to be considered complete.

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 schema fully documents the only parameter ('days') with meaning, default, and maximum, so the baseline is 3. The description adds nothing beyond the schema for the parameter, which is acceptable given the high schema coverage. No additional parameter-level semantic burden falls on the description.

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 clearly conveys that the tool reports an aggregate of what agents are asking for, sorted by demand, and includes categories with no available supply. The verb is implied rather than explicit ('aggregate of...'), but the resource and purpose are unmistakable. It does not explicitly contrast with siblings, so it is clear but not fully differentiated.

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 implies the tool should be used when someone wants to know what agents are seeking, especially where demand exists but supply does not. It provides no explicit when-to-use or when-not-to-use guidance, and it does not mention alternatives such as request_data. The 'FREE, no payment' note gives some cost context but not full routing direction.

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

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

With no annotations provided, the description carries the behavioral disclosure burden and does well: it reveals link resolution to absolute URLs, the 300-link cap, the per-link output fields, and the $0.008 USDC cost via x402 on Base. It does not detail failure modes or redirect handling, but it is far more transparent than most tool descriptions.

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?

Three sentences with no filler: the first defines the output, the second gives usage contexts, the third states limits and cost. All information is relevant 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 single-parameter link extractor with no output schema and no annotations, the description covers the key runtime facts: output fields, normalization behavior, cap, and cost. It lacks explicit edge-case behavior (e.g., pages with no links or invalid URLs), but the provided context is sufficient for an agent to invoke it correctly.

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 schema already fully documents the single 'url' parameter with type, required flag, example, and description. The tool description merely refers to 'a page' and does not add meaningful parameter semantics beyond what the schema provides, so the baseline of 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?

The description states a specific operation: extracting every hyperlink from a page, resolving them to absolute URLs, and returning anchor text and same-host status. It also groups concrete use cases (crawl an index, find the real article behind a landing page, enumerate documentation TOC), making the tool's function unambiguous and distinct from typical read/request operations.

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?

Explicit use cases are given: crawling an index, finding the real article behind a landing page, and enumerating a documentation table of contents. However, it does not explicitly mention when not to use it or name alternative sibling tools, so it stops short of full exclusion guidance.

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

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

No annotations are provided, so the description carries the full behavioral burden. It richly discloses multiple non-obvious traits: JavaScript is not executed, client-side rendered pages return their shell, blocked sites are reported honestly and not charged, and output is capped. This is exemplary transparency.

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?

Every sentence earns its place: the first states the core action and result, and the rest covers usage context, limits, behavioral caveats, and cost. The most important information is front-loaded, and there is 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 annotations or output schema exist, yet the description sufficiently covers input expectations, output content and limits, failure behavior, and cost. For a two-parameter read tool, nothing essential is missing for an agent to select and invoke it correctly.

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 100%, so the baseline is 3. The description adds practical context around maxChars by explaining why it exists ('Output is capped so it fits a prompt — raise maxChars if you need more'), but the schema already documents both parameters adequately.

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 — 'Fetch a URL and return its readable text' — and enumerates what is stripped and what metadata is returned. This clearly distinguishes the tool from general search or raw HTTP retrieval.

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 explicit guidance on when to use the tool: 'Use whenever you need the contents of a page rather than a search result about it.' It does not explicitly name sibling alternatives or state when not to use them, but the intended context is clear.

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

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

With no annotations provided, the description carries the full behavioral disclosure burden and does so well: it states the tool is free ('no payment'), that requests are catalogued for future data-building, that nothing identifying is stored, and that the response indicates service availability plus endpoint. It stops short of describing the exact behavior when no matching service exists, but the core traits are disclosed.

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?

Three sentences, each earning its place: cost, function/response, and privacy/cataloging behavior. The key differentiator ('FREE, no payment') is front-loaded, and the purpose statement precedes the caveats. Slightly verbose in the middle section, but well-organized.

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 simple single-parameter tool with no output schema and no annotations, the description covers what an agent needs: what to submit, what to expect back (availability + endpoint), and behavioral caveats (cataloguing, privacy). The only gap is the precise response structure when the service does not supply the requested data, which the absent output schema forces the description to carry.

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% and the schema already documents 'need' with an example. The description adds meaning beyond the schema by specifying that the input is freeform natural language ('in your own words') and that it accepts any data type, not just web pages, which clarifies the expected input format and scope.

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 specific action and resource: describe the data you want and receive whether the service supplies it plus the MCP endpoint. It clearly distinguishes itself from the page-focused siblings (read_page, page_links) by emphasizing 'anything, not just web pages', and the title reinforces the free-form request nature.

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?

Usage context is implied rather than explicit. 'Anything, not just web pages' signals the agent this is the general-purpose discovery tool and contrasts with the page-oriented siblings, but no sibling is named and there is no explicit when-to-use/when-not-to-use guidance or exclusion statement.

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