Extract URL to Markdown

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

Annotations already declare readOnly, openWorld and idempotent, so safety is covered; the description adds genuinely new behavior: nav/ads/footers/comments are stripped, the page is not rendered with JavaScript, and paywalled content is truncated to the public portion. It does not mention rate limits or failure modes, which keeps it below the top score.

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?

Two tightly packed sentences with no filler: the core action and output come first, the returned metadata second, and the limitations last. Every clause carries information an agent needs.

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 output schema exists, and the description compensates by naming the returned fields (title, author, publish date, word count, reading time) and the cleaned-content guarantee. Combined with full schema coverage and annotations, an agent has everything needed to call this correctly and interpret the result.

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 every parameter including defaults is already documented in the schema. The description confirms the output-format duality ('Markdown and/or plain text') and the metadata returned but adds no format syntax or limits beyond what the schema provides, so baseline 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?

States a specific verb (fetch/extract) and resource (public web page) plus the transformation applied (main content as clean Markdown/plain text). It enumerates the content types it targets (article, blog post, docs, README, Wikipedia) so the agent knows exactly what class of input this tool serves.

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?

There are no siblings to differentiate from, and the description implicitly scopes usage via 'public web page' and the explicit caveats that it does not run JavaScript and paywalled pages return only public content. That tells the agent when the result will be degraded, but it stops short of an explicit 'use this instead when' routing statement.

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