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

Beyond the readOnly/openWorld annotations, the description discloses the single-page limit, the field-level payload shape, and — unusually valuable — the two distinct failure modes: an unrecognized category returns a not-found error, while a recognized dimension with no matches returns a genuine zero-result. That disambiguates error handling the agent cannot infer elsewhere.

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?

Every sentence carries load — payload contents, encoding rules, and error semantics — and the purpose is front-loaded in the opening clause. It is dense, single-paragraph prose rather than structurally broken out, which slightly hurts scannability.

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?

An output schema exists, so return values need no further explanation, yet the description still summarizes the payload. Combined with encoding rules and error semantics, an agent has everything needed to call this correctly on the first attempt.

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?

The schema declares 100% coverage, but the embedded parameter description is visibly truncated ('e.g. \\'), so the schema is not actually usable. The tool description compensates with format rules, two concrete examples ('Room:Dorm', 'Department:Kitchen & Dining'), and the '+' / %2B encoding subtlety that is easy to get wrong. This goes beyond baseline 3, though it stops short of enumerating valid dimensions.

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 (browse), a specific resource (a Kohl's category or curated campaign page's product grid), and an explicit scope limit (page 1 only). The agent knows exactly what it gets back — normalized products with title, image, colors, pricing, rating, availability — and cannot confuse it with kohls_product_reviews or kohls_stores.

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?

Explains how to obtain further category values (every facets[].options[].category value is a ready-to-use input for a follow-up call), which is genuine chaining guidance. It does not name a sibling alternative such as kohls_suggest for discovery, nor state when-not to use it, so it falls 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.