Preview a product search (free)

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the tool returns one result, provides only a canonical link, excludes affiliate links, and requires no payment. This is useful context, though edge cases and error behavior are not covered.

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 three short sentences, front-loaded with 'FREE teaser,' and every sentence adds value: cost, output limitation, and use case. There is no filler or redundancy.

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?

For a simple one-parameter preview tool with no output schema, the description is complete. It covers purpose, usage timing, output constraints, cost, and implicitly contrasts with the paid sibling 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?

The input schema fully documents the single parameter q with a description ('What to search for') and minLength. The description adds no parameter-specific meaning, so the baseline of 3 applies due to 100% schema coverage.

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 clearly states it is a 'FREE teaser' that previews a product search, with the specific verb 'Preview' and resource 'product search.' It distinguishes itself from the sibling search_products by specifying one result and canonical link only.

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 explicitly says 'Use it to check that a query returns something before paying for the full page,' giving clear context for when to use it. It implies the alternative (full paid search) but does not explicitly name sibling tools or state when not to use it.

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