nexscope_woocommerce_product_attributesAnonymous read-only official Store API data. No merchant key or OAuth is required. Availability depends on the store version and configuration. Password-protected reviews remain hidden. Each request costs 10 credits. Failed requests are automatically refunded.
| Name | Required | Description | Default |
|---|---|---|---|
| storeUrl | Yes | Public HTTPS store root or WordPress installation path. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant operational value not covered by hints or schema. It explicitly states that the tool is anonymous (no key/OAuth required), sets a cost (10 credits), and details the refund behavior for failed requests.
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?
The description is efficient in conveying its operational constraints. Although it slightly reiterates the read-only status already found in annotations, the core information about costs and authentication is front-loaded and highly relevant.
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?
For a simple, read-only tool, it is highly complete. It covers the auth mechanism, the cost, the known limitations (reviews), and the operational contingencies (refund handling), leaving minimal ambiguity for an agent.
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?
Since schema coverage is 100%, the baseline is 3. The description adds minimal value by specifying that the URL must be the public HTTPS store root or a WordPress installation path, which helps narrow the scope of valid inputs.
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 title and name clearly identify the resource (WooCommerce Product Attributes). However, the description does not distinguish this tool from other WooCommerce API tools (like `product_detail`), relying mostly on the name to convey purpose.
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 description provides no guidance on when to use this tool over others, beyond stating its limitations (e.g., availability depends on store version or specific reviews are hidden).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.