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

Annotations already cover read-only/idempotent/non-destructive behavior. The description adds pricing per call, the $0.06 list-mode cost, output-budget reasoning, schema enforcement, and authentication options (x-credit-token header, free daily call). No contradiction with annotations.

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 description is long but front-loaded: core value proposition first, then list mode/cost, then pricing and auth. Every sentence carries distinct useful information, though some pricing details could be streamlined without losing value.

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-value details are already covered. The description sufficiently covers required inputs, both modes, field limits, pricing tiers, authentication, and the platform, which is enough for an agent to decide and invoke correctly.

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%, so the baseline is justified. The description adds meaning with a concrete fields example (price,author,published, up to 10), a clear definition of list=true as returning an array of every repeated record, and explicit mention of required inputs.

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 states a clear operation: fetch a page, strip it to readable text, and return only the requested fields as schema-enforced JSON. It also differentiates itself from raw scraping tools with phrases like 'not a pile of HTML' and 'no browser, no parser, no scraping code'.

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?

It provides clear usage context ('agents that need a fact off a page') and conditional guidance for list=true (repeated records, listings, table rows, search results). It does not explicitly name sibling tools or exclusion cases, so it falls just short of full alternative routing.

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