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 that requests are pooled across agents, that the most-wanted data gets sourced, that the call is free with no key, that it returns pointers plus a log id, and it sets a privacy constraint on inputs. It omits latency, whether the call is synchronous, and any rate limits, keeping it from a 5.

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 trigger is front-loaded in the first clause and the return/behavioral facts follow, so an agent gets the routing signal immediately. The first sentence is a long run-on enumeration, but each item is a distinct condition that earns its place, so the verbosity is functional rather than 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?

There is no output schema, and the description compensates by explaining the return payload (pointers to sources plus a log id). For an 8-parameter submission tool it covers purpose, cost, privacy, and pooling behavior adequately; the main gap is that it never explains the interplay of private/max_price_usd/freshness, which the schema carries alone.

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%, so every one of the 8 parameters is already documented in the schema and the baseline is 3. The description adds no per-parameter semantics beyond the schema, aside from a general warning not to include personal data of private individuals.

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 trigger-and-action contract: call this when data is unobtainable (403/429, CAPTCHA, login wall, no API, JS-only, PDF-only, not found) and it returns pointers to existing sources plus a log id. It is clearly distinguishable from the siblings report_failure and request_action, which are about reporting and acting rather than sourcing data.

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 when-to-use condition is exhaustively enumerated with concrete failure modes, which is unusually good routing guidance. However, it never names the sibling alternatives (report_failure, request_action) or states when this tool is the wrong choice, so it stops short of full when/when-not/alternative coverage.

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