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

No annotations exist, so the description carries full burden; it declares the tool read-only and discloses what comes back (one evidence-bearing proof result, locked ranked previews, pricing, a reusable search_id). It does not cover auth requirements, rate limits, or pagination, which keeps it short of 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?

Three sentences, purpose front-loaded, then outputs, then alternatives; no wasted text. The first sentence is dense but still readable. Slightly heavy but earns its content.

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 steps in to describe the return payload (proof result, previews, pricing, search_id), and with no annotations it supplies the read-only nature. Only auth and pagination behavior remain unaddressed, which is a minor gap for a discovery tool.

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% and the single 'query' parameter is fully documented with length bounds, constraint types, and intent. The description adds no meaning beyond the schema for the parameter itself, so 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 (search/discovery) and resource (current public or authorized web information), with the scope spelled out. It distinguishes itself from get_live_inventory, get_free_data_sample, and quote_paid_machine_job by name, so an agent can route correctly without opening schemas.

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?

Explicitly gives the selection condition (use when the request is not already covered by a known PaidHandshake inventory product) and names the alternatives for known-inventory and custom-research cases. Both the when and the when-not paths are present.

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