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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the handle is resolved to a Shopify product ID before lookup, and the storefront is fixed. It doesn't mention rate limits or empty-result behavior, but the added internals are valuable.

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, with the core purpose front-loaded and the prerequisite follow-up clearly separated. 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?

An output schema exists, so return values need not be explained, and annotations cover the read-only/open-world profile. Combined with the schema's 100% parameter coverage, the description is nearly complete; only minor gaps like pagination or empty-result behavior remain.

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 limit (default 10, max 20), handle, and intent. The description adds only the resolution note about the handle, and says nothing about limit or intent semantics. Baseline 3 is correct 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) plus resource (product recommendation items) scoped to a Fashion Nova seed handle, and distinguishes itself from sibling catalog tools by pointing to fashionnova_product/fashionnova_products for seed lookup. An agent can tell exactly what it returns 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?

Explicitly directs the agent to fashionnova_product or fashionnova_products to obtain the seed handle, which is the prerequisite for calling this tool, and notes the storefront URL is fixed (so no URL argument is needed). It lacks a when-not-to-use case, but the workflow guidance is clear.

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