nex_ip_product_list

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely new context about how the server computes charges (per quantity, duration, product days, rounded up to 2 decimals), but that billing detail belongs to ordering rather than to a list operation and doesn't describe what the listing returns or how prices are expressed.

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?

Two compact sentences with the core action front-loaded. The second sentence is arguably tangential to a listing call, but it is short enough not to bloat the definition.

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 parameters and no output schema, the description should explain what a returned 'product' contains (currency, price units, product identifiers) and how it feeds nex_ip_buy. Neither is covered, so an agent knows what the tool is but not what it yields.

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 takes zero parameters and the schema is closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 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?

States a specific verb and resource: 'List general proxy products with live prices.' The reader knows this is a read of available proxy product offerings. However, it never distinguishes itself from the nearby nex_proxy_list or nex_captcha_product_list siblings, so the boundary between 'products' and 'proxies' is left ambiguous.

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 statement of when to call this versus nex_proxy_list, nex_ip_order_list, or nex_ip_buy. The 'live prices' phrase hints at pre-purchase price checking, but that implication is never made explicit and no exclusions are given.

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