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

Annotations already cover safety (readOnlyHint=true, openWorldHint=true). The description adds only the pagination framing ('one page'), which is useful but minimal. It says nothing about rate limits, ordering caveats, or pagination bounds beyond what the schema's sort/page descriptions already imply.

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?

Two sentences, zero filler, and the core purpose is front-loaded before the sibling routing. Every clause earns its place.

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 full schema coverage, existing annotations, and an output schema, the description is sufficient for correct invocation. It doesn't mention pagination limits or the unverified sort caveat, but those live in the schema, so the gap is minor.

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 the schema already documents page, page_size, cat_id, and sort (including the sort code caveat). The description merely lists the parameter names without adding meaning. Baseline 3 applies when the schema does the heavy lifting.

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 (Fetch) and resource (one page of SHEIN product-card items for `cat_id`) with the controlling parameters named. It is immediately distinguishable from siblings like shein_products_detail and shein_products_search.

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?

Explicitly routes the agent: shein_category_nav for subcategory tabs, shein_category_filters for facet values, shein_products_search for keyword search. This is the when-to-use-vs-alternatives guidance in its ideal form.

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