kohls_product_reviews

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states the pagination behavior, the page size of 10, the normalized shape of reviews, and the edge case that a zero-review web_id returns a genuine zero-result response rather than an error. This is strong behavioral transparency without annotations.

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?

The description is compact and front-loaded; the first sentence states the operation and target, and the remaining sentences earn their place by defining the return content, the input source, and a critical edge case. There is no filler or repeated schema content.

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 the simple 2-parameter interface and absence of an output schema, the description is comprehensive enough: it covers page, page size, return fields, web_id provenance, and the zero-result behavior. It leaves minor terminal details, such as sort order or exact response shape, implicit, but nothing obstructs a correct call.

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 100%, so the baseline is already solid. The description adds meaningful parameter context beyond the schema, especially that web_id comes from a /category product response and that pagination is page-based. This will help an agent know where to source the required web_id.

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?

The description opens with a specific verb and resource: 'Browse a Kohl's product's customer reviews,' and immediately explains it returns one page of normalized review fields. It is unambiguous and distinct from the other kohls_* siblings, which handle categories, stores, and suggestions rather than reviews.

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 gives clear usage context: it returns one page of reviews for a Kohl's product, and explicitly explains that web_id is the same identifier carried by a GET /kohls/category response's products[].web_id. It does not explicitly name excluded alternatives, but with no competing Kohl's reviews sibling this is acceptable.

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