wb_prices_quarantine

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

With no annotations, the description carries the burden of explaining behavior. It usefully discloses that the new price is NOT applied, clarifying this is an informational/quarantine listing rather than a price-change action. However, it does not explicitly state that the tool returns a paginated list or that it has no side effects.

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 extremely concise and front-loaded with the priority marker and the key quarantine condition. The sentence 'Check regularly' adds practical guidance without unnecessary fluff.

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?

The tool is simple and the schema hints at list-style pagination, but the description does not explicitly state what the response represents (e.g., a list of quarantined items with pagination). It gives enough context for basic use but leaves the return contract unspecified, especially since there is no output schema.

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 0%, and the description does not explain the 'limit' and 'offset' parameters. Although their names and defaults strongly imply pagination, the description adds no parameter-level meaning, and with zero coverage the burden falls on the description.

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 identifies a specific resource ('goods in price quarantine') and a distinct business state (price cut over 3x, new price not applied). It is clearly distinguishable from other price-related siblings like wb_prices_list or wb_prices_set, though it lacks an explicit verb such as 'list' or 'get'.

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?

'Check regularly' implies a monitoring use case, and the description conveys that this tool surfaces items where the price update is pending and not applied. However, it does not explicitly state when to prefer this over price-related siblings or when not to use it.

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