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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds one behavioral note — that raw provider business fields and extensions are preserved in the response — which is genuinely useful since no output schema exists, but it says nothing about error behavior for invalid/region-mismatched IDs.

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 filler, but it leads with a generic procedural verb instead of the resource and result, so the front-loaded content is uninformative rather than efficient.

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 read-only lookup with no output schema and multiple Temu detail siblings, the description should say what detail retrieves (pricing, SKUs, seller, images) and how it differs from the duplicate geekbi/data variants. Neither is present.

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%: both goodsId (sourced from product search) and regionId ("never siteId") are fully documented in the schema. The description adds nothing on parameters, so the 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?

"Execute the selected product detail operation" restates the tool name rather than stating that it fetches full Temu product details for a given goodsId. It never distinguishes this from near-identical siblings such as nexscope_data_gb_temu_goods_detail or nexscope_temu_product_source_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?

The phrase "selected product detail operation" hints the tool is used after a search, but there is no explicit when-to-use, no prerequisite (goodsId must come from nexscope_geekbi_temu_goods_search), and no statement about which Temu detail sibling to prefer.

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