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

Goes well beyond the readOnly/openWorld annotations: it discloses that search is best-effort with fallback recommendations instead of empty results, that pagination beyond the last page yields a not-found error, and that breadcrumb/subcategory data appear only on the category listing's first page. These are non-obvious behaviors an agent actively needs.

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 the core action, but compresses a lot into one dense passage and spends significant length enumerating return contents (pricing, colorway images, variants, facet_nav) that an output schema already carries. Some of that detail is redundant, hurting conciseness.

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 two modes, the exactly-one-of constraint, pagination semantics, fallback behavior, and the presence of an output schema, an agent has everything needed to call this correctly. Nothing material is missing.

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 schema already documents page, keyword, and category. The description restates the exactly-one-of constraint (also in the schema) and adds little new syntax or format detail, so the baseline 3 is appropriate.

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 and resource ('Search Nike.com product listings') and explicitly covers the two operating modes (keyword search vs category/subcategory browse by slug). An agent can tell what the tool returns and in which mode it operates without opening the 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 the key selection rule ('exactly one of keyword or category is required') and distinguishes the two use cases, and names the slug source (nike-categories) for category mode. It does not explicitly exclude sibling tools like nike_suggest or nike_product, so it stops short of full alternative routing.

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