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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only that boilerplate is stripped and the output is LLM-ready; it says nothing about latency, rate limits, caching, or failure behavior beyond the URL restriction already documented in the schema.

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 sentence, front-loaded with the verb and resource, with the purpose qualifier trailing. Nothing is redundant 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?

For a single-parameter read tool with an output schema present and annotations covering safety, the description is nearly sufficient. The one genuine gap is routing: with ten siblings including several read/extract variants, the agent gets no help deciding when this tool is the right one.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the URL must be a public HTTP(S) page and that private/local/authenticated/paywalled resources are unsupported. The description adds no parameter syntax or format detail beyond that, 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?

States a specific verb ('extract') plus resource ('clean readable webpage text from a public URL') and even names the downstream consumer (LLM/RAG). It does not, however, differentiate itself from near-neighbors like search_extract, search_read, or web_intelligence, which an agent would need help telling apart.

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 phrase 'for LLM-ready research or RAG ingestion' gestures at the intended use case, and 'removing boilerplate' implies when it beats a raw fetch. But there is no explicit when-to-use/when-not, no mention of alternatives, and no guidance on choosing this over the sibling read/extract tools.

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