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

No annotations exist, so the description carries the full burden. It usefully discloses what is returned ('their emails, phones and social accounts') and that the corpus is Shopify/WooCommerce-specific, but says nothing about rate limits, pagination, result caps, or that with_email defaults to true and therefore silently filters results.

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?

Two tight sentences, front-loaded with the primary search behavior and followed by the alternate lookup mode. No filler, though the misleading 'price range' phrasing costs a point.

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 12-parameter tool with no annotations, no output schema and only 58% schema coverage, the description is adequate but not complete: it omits the default behaviors (with_email=true filtering, platform default 'any'), the traffic-rank meaning, and any note on result volume or pagination.

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 58% and the description compensates by naming most of the searchable axes (country, city, niche, social audience, domains) in plain language, including the social-audience filter that maps to min_tiktok_followers. It does not explain the min_rank/max_rank traffic semantics and mislabels them as 'price range', which is a real gap for a 12-parameter tool.

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?

Names a specific verb and resource ('Searches a database of millions of Shopify and WooCommerce stores') and covers both operating modes (attribute search vs domain lookup), which distinguishes it from generic contact tools like find_website_contacts. The phrase 'price range' is imprecise since the schema's rank fields are explicitly a traffic/size signal with 'no revenue data', but the core purpose is unmistakable.

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 second sentence ('Or looks up given store domains') implies the alternative mode of use, letting an agent infer that domains are for bulk lookup rather than discovery. However, there is no explicit when-to-use guidance versus siblings such as find_website_contacts or find_local_businesses, and no stated exclusions or prerequisites.

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