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

Annotations already establish that this is a non-destructive read-only operation with open-world scope. The description adds the useful behavioral constraint that no search pagination fields should be invented, but it does not describe the return shape, whether the list is exhaustive, or any auth/caching behavior.

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 description is a single front-loaded sentence with no filler. Its wording is somewhat cryptic, especially 'provider site records' and 'inventing,' but it is appropriately sized for a simple zero-parameter tool.

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, the description should clarify what a site record contains and whether this returns all Temu sites. It gives enough to avoid sending unsupported pagination parameters, but leaves the actual return content underspecified for an agent deciding whether to call it.

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 tool has zero parameters and the schema is fully described, so the baseline is high. The description reinforces this by warning against adding search pagination fields, which is relevant semantic guidance for a zero-param list operation.

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 to 'Return provider site records,' which identifies a read/list operation, but 'provider site records' is vague and does not explicitly say these are Temu sites. The title supplies 'Temu Site List,' but the description itself does not clearly distinguish this from the many other Temu listing tools.

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 explicit guidance on when to use this tool versus the sibling Temu tools such as nexscope_geekbi_temu_mall_search or nexscope_data_gb_temu_site_list. The only usage-adjacent instruction is not to invent pagination fields, which is a constraint rather than a selection guideline.

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