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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no pagination defaults (pageSize 1-100, page starting at 1), no note that all filters are AND-combined, no indication of what 'marketplace performance metrics' contains or how large result sets behave.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terseness is more a completeness problem than a conciseness win.

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 24-parameter filtering/ranking tool with no output schema, one sentence is far too thin: the agent gets no sense of the response shape, default page size, ranking default, or how filters combine. Everything must be reverse-engineered from the schema alone.

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% and each of the 24 properties has an inline description with examples, so the schema carries parameter semantics entirely. The description contributes nothing extra (e.g., that beginSales/endSales pair into a range, or that sortBy/sortDesc interact), so 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?

States a specific verb and resource ('Returns Etsy store profiles and marketplace performance metrics'), which is enough for an agent to pick it over nexscope_etsy_product_query or nexscope_etsy_product_detail. However, it never acknowledges that this is a filtered store-search/list tool (country, category, sales/review/favorite ranges, sorting) nor how it relates to the near-identical sibling nexscope_data_eh_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?

No when-to-use guidance at all: nothing says to use this for store-level prospecting versus product-level lookups, no prerequisites, no note about when a store name search vs. a metric-filter search is appropriate. Among 24 optional filters the agent is given no routing advice.

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