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

Annotations only say readOnly/openWorld; the description adds a lot beyond that: a truncated free-tier result with paid upgrade links, two payment paths (x402 via Apify with no account, or Bearer tt_… billed in TidyTools credits), and concrete quota numbers (3/IP/UTC day, 50 shared ASN pool, 100 global). These are the operational facts an agent needs before calling a rate-limited, paid-tier tool.

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?

The core purpose and the one-URL constraint lead, with pricing and quota detail compressed into dense trailing clauses. It is information-rich rather than padded, though the payment/billing sentences are terse enough to feel like a wall of fragments rather than prose.

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, the description does carry the burden of describing returns — it says main text plus metadata and warns that free results are partial and upgrade links are included. Auth and quota are fully covered; what those "metadata" fields actually are remains unspecified, a minor residual gap.

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 coverage is 100% and there is only one parameter, so the schema already documents the single `url` field. The description adds only the implicit "one URL, not many" framing, which barely extends beyond "One public HTTP(S) URL." 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 and resource ("Extracts one article's main text and metadata") and pins the scope to a single URL. It differentiates itself from batch/monitoring use but never names the closest siblings (summarize_article, read_url, smart_fetch), so an agent must still infer which extraction-flavored tool it wants.

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?

"Use for one url. Not for batch work or unrestricted monitoring" gives both the positive case and an explicit exclusion. It stops short of naming an alternative tool to use instead when batch or summarization is the goal, which is what a 5 would require.

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