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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. Beyond that the description discloses real behavioral traits: page 1 only (no pagination), an unrecognized category returning a not-found error rather than an unfiltered listing, and a recognized-but-empty dimension returning a genuine zero-result response. It omits auth/rate-limit context, so not a 5.

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 purpose, then syntax, then error semantics — a logical order with little filler. It is a single dense paragraph that slightly over-enumerates product fields already covered by the output schema, but nothing is egregiously wasteful.

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 one-param read tool with an output schema and read-only annotations, everything an agent needs to call it correctly is present: exact category syntax and encoding, scope (page 1 only), and both error modes. Return values are covered by the output schema and reinforced in the description.

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 0% and the single required param is a bare string, so the description carries the full burden and does so well: it defines the taxonomy form ('Room:Dorm', 'Department:Kitchen & Dining'), the multi-dimension '+' combination, and the '%2B' percent-encoding needed to survive decoding. This is meaningfully beyond 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 ('Browse') and resource ('a Kohl's category or curated campaign page's product grid'), and enumerates the returned fields (title, image, colors, pricing, rating, availability). An agent can distinguish this from siblings like kohls_product_reviews, kohls_stores, and kohls_suggest 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?

Gives clear usage context: page 1 only, the 'category is Kohl's own catalog taxonomy' constraint, and how to source follow-up category values from facets. It does not name an explicit alternative (e.g. kohls_suggest) or state when NOT to use this tool, so it stops short of full routing guidance.

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