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

The annotations declare readOnlyHint=false and openWorldHint=true, which is important because it implies that the tool may modify state. The description instead calls it a 'fixed read-only provider path,' which conflicts with readOnlyHint=false and leaves the actual safety profile ambiguous. It also discloses nothing about pagination limits, quota behavior, or what happens when multiple selector fields are supplied.

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?

It is a single front-loaded sentence with no filler, so it is structurally efficient. However, that brevity reflects under-specification rather than genuine conciseness, because the one sentence carries almost no actionable content.

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 tool with a rich, mutually-exclusive selector schema, no output schema, and annotations that leave the write versus read behavior unclear, the single-sentence description is far too thin. An agent cannot tell what data comes back, which selector to use, or what the 'provider path' constraint means.

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?

The schema exposes a large nested 'snapshots' object with six alternative identifier fields (keyword, category_id, sku_id, product_url, shop_id, shop_query) and many filter/sort fields, but the description explains none of them. The anyOf structure leaves it unclear whether exactly one or several selectors may be combined, which is precisely the kind of ambiguity the description should resolve; it adds no meaning at all 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 says it 'returns normalized public ecommerce research data,' which restates the title 'Mercado Market Intelligence' in generic terms. It never names the resource being researched (products, shops, keywords) and never mentions Mercado Libre or the market codes, so it gives no basis for distinguishing this tool from the sibling nexscope_mercado_product_selection.

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?

There is no guidance on when to use this tool instead of nexscope_mercado_product_selection or any other Mercado sibling, and no stated prerequisites such as needing a keyword, category, SKU, URL, or shop identifier. The agent is left to infer usage entirely.

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