Fetch a web page, render it in a headless browser, and get a local markdown file with readable content and embedded images.
Fetch and render a web page. Returns the absolute path to a local markdown file containing the page content with downloaded images embedded as local file paths.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Target page URL. |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral weight. It discloses the key output behavior (markdown conversion, image embedding, local file path), but does not mention potential network side effects, JavaScript rendering, page size limits, or error behavior. This is a moderate gap for a tool that fetches external pages.
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 one efficient sentence that front-loads the action ('Fetch and render a web page') and immediately states the concrete return value. Every word contributes necessary information.
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 tool with no output schema, the description adequately covers what the agent receives (a markdown file path) and what the tool does. It could additionally mention usage limitations or cleanup expectations, but nothing critical is missing for basic 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?
The input schema has 100% description coverage: the single 'url' parameter is documented as 'Target page URL.' The description adds no further semantic detail beyond the schema, so the baseline score of 3 is appropriate.
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 identifies a specific verb (fetch and render) and resource (web page), and clearly states the output: a local markdown file path with embedded images. With no sibling tools, there is no differentiation burden, and the purpose is unambiguous.
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 provides clear context about what the tool does, so an agent can infer when to use it. However, it does not explicitly state when not to use it or name alternatives, though none exist in the provided sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.