run_target_products_reviews

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

With no annotations, the description carries the full burden. It adds two genuinely useful behavioral facts beyond the schema: results are ordered newest-first and cost 1 credit per returned record. It stops short of describing what a review record contains, whether pagination is driven by start_page/max_items together, or any auth/rate-limit behavior.

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 sentences, no filler, and the most decision-relevant information (what it fetches, how to identify the product) is front-loaded before the cost/ordering note. Every clause earns its place.

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?

There is no output schema and no annotations, so the description is the only source of behavioral context. It covers ordering and cost but says nothing about the shape of a review record or how start_page interacts with max_items, leaving the agent to infer the return payload.

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 'product', 'max_items', and 'start_page' are already documented in the schema. The description restates the identifier format ('by TCIN or URL') and adds ordering, but nothing new about the two pagination parameters, 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?

Names a specific resource (customer reviews), the target platform (Target), and the keying input (TCIN or URL), so an agent can immediately tell it apart from run_target_products and run_target_products_questions. It does not explicitly call out those siblings, but the resource noun 'reviews' is distinguishing enough.

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 states what the tool returns but never says when to choose it — no mention of prerequisites (e.g. needing a TCIN from run_target_products_search first) and no comparison to sibling tools like run_target_products_questions or run_walmart_product_reviews. Usage is only implied by the resource name.

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