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 behavioral facts beyond the annotations: the AND combination semantics and that a zero-match query returns a well-formed empty result rather than an error.

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?

Dense but front-loaded with the core purpose, and each sentence carries information. The 'unlike some other families'...' clause is slightly verbose and could be tightened, but there is 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?

An output schema exists, so return values need no explanation, and the description fully covers search-vs-browse semantics. The remaining gap is the unexplained pagination and price parameters, which matters for a 10-parameter tool.

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 0% across 10 params, so the description carries the burden. It meaningfully explains q, department, material, and color (combination logic and where facet values come from) but says nothing about page, size, limit, category, min_price, or max_price, leaving pagination and pricing undocumented in both places.

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 ('Search or browse Quince's product catalog') and names the underlying index, which distinguishes it from quince_product, quince_categories, and quince_suggest. An agent can tell what this tool covers 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?

Explains that q and facet filters combine as an AND and that omitting every field browses the full catalog, which covers the main usage decision. It points to quince_categories for valid facet values but never names sibling alternatives like quince_suggest for autocomplete, so it stops short of explicit when-not guidance.

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