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

Beyond the readOnly/idempotent/openWorld annotations, it discloses that data comes via web_search from third-party review sites, that results are cached for 2 days (explaining why stale data may appear and what force_refresh is for), and that a business-profile brand_name is required. Return shape is not described, but no output schema exists to cover it.

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?

Front-loads the purpose, then sources, then filter guidance, then prerequisites/caching. Dense but no filler sentences; the title line slightly duplicates the opening sentence.

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 4-parameter, zero-required, read-only research tool, it covers purpose, sources, filtering strategy, prerequisites, and cache behavior. The main omission is what a review record contains (rating, text, source, date), which matters since there is no output schema.

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 75% and the rating_filter enum already documents the star mappings the description repeats. The only genuine additions are the caching rationale behind force_refresh and the framing of negative reviews as creative angles; brand_name and ad_account_id semantics are essentially restated from the schema.

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 and resource ("Search public customer reviews about the brand") and names the actual sources (Trustpilot, Judge.me, Google Reviews). This clearly distinguishes it from siblings like fetch_ad_comments and search_reddit, which target different corpora.

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?

Gives concrete selection logic for rating_filter — positive for what customers love, negative for objections and creative angles — and states the prerequisite that brand_name must exist in the business profile. It does not explicitly name a sibling alternative (e.g. fetch_ad_comments vs public reviews), so it stops short of a 5.

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