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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely useful behavior by disclosing the two distinct data sources selected by presence/absence of style_code. It doesn't cover rate limits or pagination, but the mode-switching behavior is the key trait.

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-loads the core purpose in the first clause, then explains the parameter semantics in a tight second sentence. Dense but every clause carries information, with no filler.

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?

With an output schema present, return values needn't be described, and annotations cover the safety profile. The description covers purpose, both modes, and style_code sourcing; the only real gap is the undocumented 'max' parameter.

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%, so the description must carry parameter meaning. It thoroughly explains style_code (set = product carousel, omitted = trending; value sourced from gucci_search/gucci_category) but says nothing about the 'max' parameter, leaving one of two parameters undocumented.

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+resource: a Gucci recommendations shelf returning normalized product summaries, and it distinguishes its two modes (product carousel vs trending shelf). It also points to the sibling tools (gucci_search, gucci_category) that supply style_code, though it does not explicitly position itself against other product-listing tools like gucci_product.

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 explicit conditional guidance: set style_code to get a given product's 'You May Also Like' carousel, omit it to get the general trending-items shelf. This is clear context for both modes, but it never states when to prefer another tool or when not to call this one.

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