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

The description frames the tool as a read-style query/search/view operation, but the annotations declare readOnlyHint=false. That directly contradicts the described non-mutating behavior, and the description does not clarify the discrepancy or add other behavioral context such as output shape or constraints.

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 front-loaded with the core action and filter dimensions, then follows with trigger guidance. The second sentence is lengthy and trigger-keyword-heavy, but it remains purposeful for routing.

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 28-parameter query tool, the description covers the main filter dimensions and usage triggers, while the schema covers each parameter. However, with no output schema and contradictory annotations, the description does not describe return behavior, pagination expectations, or authentication/rate-limit context.

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 the schema already documents all 28 parameters in detail. The description adds a useful high-level grouping of filter dimensions, including keyword/URL, price, sales, favorites, reviews, listing date, category, product type, and tags, but does not add parameter syntax or encoding details beyond the schema.

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 a specific verb and resource: "Query Etsy products" and lists the multi-dimensional filter categories. It is clearly a product search/filter tool rather than a detail or store tool, though it does not explicitly name the relevant siblings such as nexscope_etsy_product_detail or nexscope_etsy_store_query.

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?

It gives strong trigger conditions: Etsy products, listings, sourcing, bestsellers, handmade, vintage, items, and product query, even when the tool name is not mentioned. It does not state when not to use this tool or name an alternative for detail/category/store-specific needs.

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