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

With no annotations, the description carries the full burden and does well: it discloses the data source (saved 30-day aggregates), the qualifying thresholds (300+ runs, 20+ users), that evidence includes snapshot date and age, and explicitly disclaims live testing or currency guarantees. It lacks any note on auth requirements or read-only nature, but the staleness/limitation disclosure is strong.

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 thresholds are front-loaded in the first clause, with the caveat sentence following naturally. It is dense but every element (thresholds, alternatives, snapshot age, live-test disclaimer) earns its place; 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?

No output schema and no annotations exist, so the description must explain returns, and it does: it names the primary pick, the alternative categories, and the evidence fields (snapshot date and age). The remaining hole is the undocumented 'site' parameter, which keeps it short of complete.

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?

There is one required parameter, 'site', with 0% schema description coverage, so the description must compensate. It never mentions the parameter at all, leaving ambiguous whether 'site' is a domain, a hostname, a website ID from list_websites, or a display name. This is a real gap for the only input.

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 (Recommend) and resource (scrapers/tools for a site), and enumerates the selection criteria: highest recorded success rate among tools with 300+ runs and 20+ users, plus most-used and cheapest alternatives. It is distinguishable from compare_* siblings (which compare) and find_scrapers (which locates), though it never names them 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?

The description implies usage context by framing results as historical aggregate recommendations (-day window) that are explicitly not a live execution test, which tells the agent when the data is trustworthy. However, it never states when to prefer this over siblings like compare_scraping_apis or find_scrapers, and gives no prerequisites or exclusions.

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