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

With no annotations, the description carries the full disclosure burden. It does disclose a genuinely useful conditional auth behavior ('Bearer becomes required when passing phone') and 'browse' weakly implies a read-only operation. However, the auth caveat largely duplicates the phone parameter's schema note ('REQUIRES bearer auth'), and the description is silent on pagination behavior, return shape, rate limits, and explicit read-only status.

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 with zero filler. The purpose and filter list are front-loaded in sentence one, and the conditional auth caveat occupies sentence two. 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?

The tool is moderately complex (9 optional params, 2 enums) with no output schema and no annotations. The rich schema descriptions compensate for much of what the top-level description omits, but nothing describes the return format (only near_hex's schema note hints at a shade_match field) and the read-only safety profile is never explicitly stated. Adequate with clear gaps.

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% and the per-parameter descriptions are unusually rich (cross-lingual semantics for q, ΔE and shade_match for near_hex, the must-be-paired constraint for hue_family), so the schema carries the load. The description adds only marginal gloss — 'ΔE shade match' and 'rewards projection' — which nudges but does not transform understanding. 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 pair ('Browse the catalog') and enumerates the main filter dimensions (tag, brand, near_hex, hue_family, sort), so the tool's job is immediately identifiable. The product catalog resource is clearly distinct from sibling tools (cart, customer, orders, gift cards), though no alternative is explicitly named.

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?

Usage context is implied rather than stated: an agent infers 'use this when a catalog/product lookup is needed' from 'Browse the catalog,' which is adequate but not explicit. No exclusions, prerequisites, or alternative tools are named, and the top-level description gives no when-to-use/when-not-to-use selection guidance.

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