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

With no annotations, the description carries the full behavioral burden, and it does add one genuinely useful fact: the metered pricing model ("5 free trial calls per signed wallet"), which signals that a signed wallet is required and calls are limited. It says nothing about rate limits after the trial, timeouts, page-size limits, JS rendering, or failure behavior for unreachable URLs.

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 plus a billing tag, with the core capability front-loaded. It is tight and wastes little space, though the emoji/promo fragment is not strictly informational for an agent deciding how to call it.

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 one-parameter tool with no output schema, the description conveys input (a URL) and output shape (clean text), so an agent knows what comes back. What is missing is only edge-case behavior and the distinction from the other scraping siblings, which keeps it out of 5.

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% for the single url parameter, so the schema already documents it; the description adds no format details (scheme requirements, redirects, encoding) beyond restating that the URL is what gets processed. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb+resource ("Web Scrape: Clean text from URL") and identifies the tool as an alias of text-scrape, which tells an agent it is interchangeable with that sibling. It does not differentiate itself from the other scraping siblings (browser-scrape, html-text-extract, web2md, premium-web-scrape), which is why it stops short of 5.

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?

"alias of text-scrape" implies either tool can be used for the same job, which is implicit routing guidance. However, there is no statement of when to prefer this over browser-scrape or html-text-extract, no precondition about page type (JS-heavy, static), and no exclusions. Usage is implied rather than stated.

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