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

The description asserts a 'read-only provider path' while the annotations declare readOnlyHint=false — a direct conflict an agent cannot resolve from the text. Nothing is disclosed about supported marketplaces, rate limits, or failure modes for an openWorldHint=true tool.

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 short sentence with no padding, so it is structurally efficient. The problem is under-specification rather than verbosity — the one sentence carries almost no information.

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, one undocumented parameter, and annotations that conflict with the text, the description should explain what data is returned, which Shopee regional domains are accepted, and the URL requirement. It does none of these, leaving the agent unable to call the tool correctly from the description 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 0% for the single required productUrl parameter. The regex pattern constrains hostnames and the '-i.<shop>.<item>' URL shape, but the description contributes no meaning about what the parameter represents or how to obtain a valid value.

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 only that it 'Returns normalized public ecommerce research data' — it never names Shopee, product pages, or a product-detail verb. The resource and operation are inferable only from the tool name and title, so the description is effectively a restatement of the title in generic boilerplate.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as nexscope_shopee_product_search (finding a product) or the several other Shopee detail tools in the sibling list. 'Fixed read-only provider path' hints at exclusivity but explains nothing actionable.

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