Read a webpage as Markdown and optionally save it to a named library for offline recall and reuse later.
Read a webpage as Markdown, optionally save to library
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to read | |
| save | No | Library to save into (omit to just read) |
Changes observed during successful MCP inspections.
v0.1.0Does 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 does disclose the dual read/save mode, but that same information is already in the schema's save parameter, and it says nothing about fetch failures, permission/auth needs, rate limits, or whether saving overwrites existing library entries.
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?
One compact, front-loaded sentence with no filler and the primary action stated first. It is arguably under-specified rather than over-long, but the structure itself is efficient.
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 two-parameter tool with no output schema, the description covers the core action and the Markdown return format. It omits what a 'library' value means, what the default save destination is, and error behavior, leaving meaningful gaps.
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% and both parameters are documented in the schema, so the baseline of 3 applies. The description restates the read/save distinction but adds no format, default, or destination-library semantics beyond what the schema already provides.
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 ('Read'), resource ('a webpage'), and output format ('as Markdown'), plus the optional save behavior. It is clear what the tool does, but it never distinguishes itself from plausible siblings like mind_browse or mind_ingest.
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 'optionally save to library' phrasing implies when to pass save versus omit it, which is useful implied guidance. However, there is no explicit when-to-use-this-vs-alternative statement (e.g., mind_browse or mind_ingest), so routing relies on inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.