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

The description adds behavioral context beyond annotations (readOnlyHint, idempotentHint, destructiveHint) by stating it is fixture-backed, uses no live Shopify calls, and does not affect cart behavior. No contradictions.

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 key purpose and constraints, followed by usage guidelines and a specific rule. However, the sentence about FoV is somewhat repetitive and could be streamlined.

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?

Given no output schema, the description does not describe the return format (e.g., product details, pagination). It explains behavior well but lacks details on query semantics or the meaning of 'limit'. The extra fields in 'catalog' (additionalProperties) are unaddressed.

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?

With 50% schema description coverage, the description does not elaborate on the 'meta' or 'catalog' parameters, missing an opportunity to clarify their usage. The description only implies 'broad discovery' relates to query, but provides no additional semantic value beyond the schema's basic descriptions.

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 clearly identifies the tool as a 'Fixture-backed UCP Catalog search alias for Shopify-native product discovery', specifying the verb (search) and resource (UCP catalog). It distinguishes from siblings by noting it is for broad discovery and not for sensor/FoV tasks.

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 states when to use—'only for broad discovery'—and when not to—'when a sensor or target FoV is involved'—providing alternative tools (match_lens_to_sensor, calculate_field_of_view). This is exemplary guidance.

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