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

No annotations are provided, so the description carries the full burden. It usefully discloses ordering ('newest first') and cost ('1 point per returned record'), but says nothing about authentication requirements, pagination behavior across start_page/max_items, or what a returned record contains.

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 short sentences, zero filler, with the resource and ordering front-loaded ahead of the billing note. Every clause carries information.

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 read-only reviews fetch with no output schema and no annotations, the description covers the essential scope, ordering, and cost. It stops short of explaining return fields or how pagination interacts with max_items, which would round it out.

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%, so the schema already documents product, max_items, and start_page fully. The description's mention of TCIN/URL adds no format detail beyond the schema's own example, so the 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+resource ('Customer reviews of a Target product') with input formats (TCIN or URL) and a scope qualifier ('newest first'). It is clearly distinguishable from siblings like run_target_products_questions, run_target_products_search, and run_target_products_recommendations without opening any schema.

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, no prerequisites, and no routing versus the many sibling review tools (e.g., run_walmart_product_reviews, run_ebay_product_reviews) or versus Target's own questions/search tools. The resource is narrow enough to infer intent, but nothing is stated.

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