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

With no annotations, the description carries the full burden and does add real behavioral context: server-side Mozilla Readability processing, boilerplate/nav/ad stripping, first-party provenance with no third-party reselling, and an implicit scope limit to public pages. What it omits is failure behavior — paywalled, JS-rendered, or authenticated pages, plus any rate limits or error modes.

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, front-loaded with the core action and return payload before the use cases. The closing line about not reselling a third-party reader service is slightly promotional, but it does carry provenance information, so it roughly earns its place.

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?

With no output schema and no annotations, the description steps in to describe the return shape (title, excerpt, body text), which is exactly what is missing elsewhere. What remains uncovered is error/limit behavior for non-public or dynamic pages, a minor gap for a single-parameter extraction tool.

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 0% and the single 'url' parameter has no format, validation, or example in the schema. The description partially compensates by saying 'send a URL' for 'any public web page', which conveys the accepted value domain, but adds no syntax or edge-case guidance.

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?

Specific verb ('extract') plus resource ('readable main content of any public web page') and an explicit statement of what comes back (page title, excerpt, body text). The 'as clean text' framing also implicitly separates it from the sibling text-to-structure tool, which produces structured output.

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?

It lists target scenarios (RAG ingestion, summarization, research, page monitoring), which implies when the tool is appropriate, but never states when NOT to use it or names an alternative. The nearest sibling, text-to-structure, is never referenced, so the agent must infer the routing itself.

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