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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description usefully adds that only 'public' articles and 'readable' body paragraphs are returned, implying paywalled/malformed content may yield partial results, but it says nothing about extraction failures, redirects, or rate limits.

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?

A single front-loaded sentence with no filler; the resource and the input constraint both land in one pass.

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?

An output schema exists, so return structure need not be described, and annotations carry the safety profile. What remains is the one-URL contract, which the description covers; only edge-case behavior (paywall, non-article page) is unstated.

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 100% schema coverage the baseline is 3, but the description adds a constraint not present in the schema: the URL must live under the /news path, not just any thenextweb.com page. That narrows the accepted input meaningfully.

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') and a concrete resource split into two parts: 'article metadata' and 'readable body paragraphs'. The scope ('a canonical thenextweb.com/news URL', singular article) implicitly separates it from sibling feeds like thenextweb_headlines and thenextweb_news, though no sibling is named explicitly.

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?

Usage context is implied: use it when you already have a canonical The Next Web article URL. There is no statement of when not to use it, no named alternative (e.g. thenextweb_headlines for discovery), and no prerequisites or failure conditions.

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