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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds real value beyond that: it discloses the paged envelope ({total, count, offset, limit, items}) and maps the tool to the underlying Ecwid REST endpoint GET /products. It does not mention default page size or rate limits, leaving a small gap.

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, front-loaded with the verb and resource, then the return contract and endpoint. No filler, no repetition of the schema, every clause carries information.

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?

With no output schema present, the description compensates by describing the paged result envelope explicitly. Combined with the 100%-covered input schema and the readOnlyHint annotation, an agent has everything needed to construct a filtered, paginated, sorted query.

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%, so every parameter (sku, limit, offset, sortBy enum, enabled, inStock, keyword, priceFrom/priceTo, category) is already documented in the schema. The description only reconfirms the filter families and sorting, adding no syntax or format detail beyond the structured fields — the 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?

Names a specific verb+resource ('Search / list the store's products'), enumerates the filter dimensions it accepts, and states the return shape. This clearly separates it from retrieval siblings like ecwid_get_product, which an agent can infer is the single-item counterpart.

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?

The phrase 'optional filters' implies the tool works with or without narrowing, and the keyword/SKU/category/stock/price list hints at typical use. However, it never states when to prefer this over ecwid_get_product or ecwid_list_categories, and gives no exclusions or prerequisites.

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