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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered elsewhere. The one additive clause, 'preserve provider business fields and extensions,' vaguely hints at pass-through output but says nothing about result shape, pagination behavior, or the page×size≤10000 cap beyond what the schema states.

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?

One short sentence with no bloat, which is good, but it is front-loaded with filler rather than the operation's actual scope. Brevity here comes at the cost of substance rather than from efficiency.

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?

A 24-parameter, open-world search tool with no output schema requires the description to explain what is searched, what comes back, and how to choose it over the other Temu tools. The description covers none of this, leaving the agent to infer scope from the parameter list 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% across all 24 parameters, each with bounds and semantics (e.g., 'Temu region from sites[].regionId; never siteId'), so the schema does the heavy lifting. The description adds nothing about parameters, which is acceptable at the baseline but earns no credit.

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 title rather than describing the operation: 'select shop search operation' is essentially the name 'Temu Shop Search' reworded. It never states that it searches Temu shops/malls (vs. products or categories), so an agent cannot separate it from siblings like nexscope_geekbi_temu_goods_search, category_search, or keyword_search.

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 (e.g., obtaining regionId from sites[] or catIds from category lookup, which the schema hints at), and no mention of alternatives. 'Execute the selected shop search operation' presupposes a selection the agent has no way to reason about from this text.

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