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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this makes a non-read-only call against an open-world source, but the description supplies nothing further. It does not say the endpoint accepts an image URL, whether it fetches external images, rate limits, or what gets returned — all behaviour an agent would need for a call flagged non-read-only.

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 text is short but that brevity reflects under-specification rather than economy — it is a title fragment duplicated as a description, with nothing front-loaded about inputs, behaviour, or results.

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 an image-search tool taking a required imageUrl and returning (presumably) visually similar Temu products with no output schema, the description should indicate what results look like and any input constraints. None of that is present, leaving the agent dependent on 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%, so both imageUrl and contentType are already documented in the schema, which sets the baseline at 3. The description contributes no parameter meaning of its own beyond the title.

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 restates the tool title verbatim: "Temu Intelligence GB: temu/goods Image Search API." It conveys the resource (Temu goods) and hints at an image search verb, but adds no explanation of what an image search actually does. An agent must infer its behaviour entirely from the name.

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 instead of siblings such as nexscope_data_gb_temu_goods_search, nexscope_data_alibaba1688_image_search, or nexscope_reverse_product_image_search, all of which could plausibly serve a similar need. The only signal is the word "Image" in the name.

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