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

Adds substantial behavior beyond the annotations: 30-90 second latency (longer via Bright Data), on-demand sampling without a user cookie, sort ordering only guaranteed within the returned sample, no guarantee that the listing's newest 100 are returned, a 7-day cache, and an explicit disclaimer that heuristics do not prove authenticity. This is unusually rich disclosure for a network-backed tool.

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-loaded with the most decision-relevant fact (latency and sample size), and each following clause carries a distinct caveat with no filler. Slightly dense run-on phrasing, but nothing is wasted.

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?

Given there is no output schema, the description still arms the agent with the operational facts it needs: duration, sample scope, cache lifetime, sort reliability, and an explicit caveat that the authenticity signal is heuristic. The only missing piece is the shape of the returned analysis, which is a modest gap.

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 67%; retailer and product_id are documented in the schema itself. force_refresh has no description anywhere, and the description only implies its meaning through 'Cached for seven days' without naming or explaining the override. Marginal added value over 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 (analyzes) and resource (reviews), with scope quantified as 'up to 100 recent reviews' and a hint at the analytical angle (heuristics/authenticity). However, it never says what the analysis actually returns (sentiment, authenticity score, themes), and it does not distinguish itself from the sibling check_product_trust, which sounds like an overlapping review/trust analysis.

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?

No when-to-use guidance and no comparison against siblings such as check_product_trust or check_store_score. The only conditional context is operational (on-demand sampling, 7-day cache), not selection guidance for the agent.

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