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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds non-obvious edge-case behavior: out-of-range pages return a normal result with an empty products list rather than an error, and an unrecognized category/cdp_hash pair yields a not-found error. Auth requirements and rate limits are not mentioned, keeping it below 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 the core action, then URL construction, then pagination/error semantics. Every sentence carries distinct information with no redundancy.

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 not be described, and the description covers parameters, pagination boundaries, and error cases. Nothing essential for correct invocation 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 baseline is 3. The description goes beyond the schema by giving the exact URL template and concrete example values (women-new-styles, n14f1wz6o10), clarifying how the two path-segment parameters are formed.

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 ('Browse a lululemon category's product listing') and enumerates what the listing contains (pricing, sale detection, sizes, colors, style numbers). This clearly separates it from sibling lululemon_product (single item), though it never names or contrasts siblings explicitly.

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?

Usage is implied rather than stated: the description explains how category and cdp_hash are derived from a category URL, which tells the agent when this tool applies. However there is no explicit when-to-use/when-not guidance against alternatives like lululemon_categories or lululemon_product.

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