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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description usefully adds that no store key or OAuth is needed, anonymous store pricing applies, each request costs 10 credits and failures are refunded. That cost/auth context is exactly the extra value the description should carry. It does not describe the response shape, which keeps it below 5.

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 before the operational (auth, pricing, credits) details. No filler, though the multi-mode opening sentence is the least load-bearing part given the parameter set.

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, the description should say something about what comes back (product list fields, pagination totals). It also never explains how the three advertised modes are selected, given there is no product-id parameter. Cost and auth are covered, but the operational picture is incomplete.

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 parameters are already documented with bounds and defaults. The description only restates the single-store scoping already implied by storeUrl and adds nothing about keyword matching behavior (exact vs fuzzy) or how paging interacts with results.

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 names a resource (WooCommerce products) and several verbs (search, inspect, retrieve parent SKUs), but the schema exposes only storeUrl, keyword, pageNum and pageSize, so 'inspect a product' and 'retrieve a parent's SKUs' are not actually reachable through this tool. An agent can tell it is a store-scoped product lookup, but the stated modes overstate what the parameters support.

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?

No guidance on when to pick this over the many WooCommerce siblings present (nexscope_woocommerce_product_detail, nexscope_woocommerce_product_variations, nexscope_woocommerce_product_categories, etc.). The overlap with product_detail is especially problematic: the description claims 'inspect a product' without saying why you would not just call product_detail.

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