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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the storefront URL is fixed server-side and empty result pages return HTTP 200 with an empty products array, which helps an agent interpret pagination edge cases.

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 behavioral notes, then the sibling pointer; every sentence is informative. It partially duplicates the schema's parameter text, which is slight waste, but overall it is tight and well ordered.

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 explained, and the description covers pagination, empty-page behavior, and sibling routing. It is complete enough to invoke correctly, missing only richer guidance on how it compares to the other Kylie Cosmetics listing tools.

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 description coverage is 100%, so both parameters (page, limit) are already fully documented in the schema. The description merely restates the same limits and defaults, adding no syntax or semantic detail beyond what the schema provides. Baseline 3 applies.

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?

The description opens with a specific verb+resource ("Returns normalized products from Kylie Cosmetics's public product catalog") and explicitly distinguishes itself from the sibling kyliecosmetics_collection_products. An agent can tell it apart from other Kylie Cosmetics catalog tools without opening a 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?

It names the alternative tool (kyliecosmetics_collection_products) and the condition that selects it (listing collection products). This gives clear routing context, though it doesn't cover the full set of alternatives (e.g. kyliecosmetics_product, search_suggest) or state exclusions explicitly.

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