search_products

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the meaningful connector prerequisite, but says nothing about pagination via cursor, the 20-item limit cap, or result ordering behavior that an agent calling a paged search needs.

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 short sentences with the core operation front-loaded and the prerequisite second. No waste, though at this level of schema under-documentation the brevity is closer to under-specification than elegance.

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?

A 7-parameter, paginated, price-filtered search with 0% schema coverage and no output schema demands more than a one-line description. Missing pagination semantics, currency/country format expectations, and price-unit explanation leave real 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 0% across 7 parameters, and the description only gestures at query/country/currency without format (ISO-2/ISO-3) or intent. limit, cursor, min_price_minor and max_price_minor are entirely unexplained in both places, so the description fails to compensate for the coverage gap.

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 (Search) plus resource (Shopify catalog products) and the dimensions it filters by (query, destination, currency). It implicitly distinguishes itself from get_product and compare_offers, though it never names a sibling to sharpen the boundary.

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?

Gives one concrete prerequisite (an enabled catalog connector) but no guidance on when to choose this over compare_offers or get_product, and no note on when a search is inappropriate. Usage is implied by the word 'Search' rather than explained.

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