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

The description adds genuinely useful operational context that annotations do not: no store key/OAuth required, anonymous pricing, 10 credits per request, and automatic refunds on failure. However, the described behavior is entirely read-only (search/inspect/retrieve) while annotations declare readOnlyHint=false, an inconsistency an agent may misread as a mutating call; flagged as an annotation contradiction.

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?

Four short sentences, front-loaded with the capability statement before the auth and cost details. Nothing is padded, though 'Anonymous store pricing applies' is vague enough that it doesn't clearly earn its place without further explanation.

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?

Auth requirements, credit cost, and refund policy are covered, which is valuable for a paid open-world call. But with no output schema, the description should say more about the response shape (list vs. single product) and clarify which parameter triggers the 'inspect a product' and 'parent SKUs' modes, since the schema provides no such selector.

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 storeUrl, keyword, pageNum, and pageSize are fully documented in the schema and the baseline is 3. The description adds little parameter-level meaning and actually hints at modes ('inspect a product', 'retrieve a parent's SKUs') that the schema exposes no identifier parameter for, which could confuse an agent about what to pass.

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 uses specific verbs and resources — search, inspect a product, retrieve a parent's SKUs — all scoped to one WooCommerce store's public Store API. It is clear what the tool does overall, but it does not distinguish itself from close WooCommerce siblings like nexscope_woocommerce_product_detail or nexscope_woocommerce_product_variations, which cover much of the same ground.

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 is only implied: the reader infers that a storeUrl plus keyword yields search results, and that this is for public Store API data only. No explicit when-to-use/when-not conditions or named alternatives (e.g. the product_detail or variations tools) are given, so routing depends on inference.

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