Массовое обновление цен

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

Beyond annotations, the description discloses critical behavioral details: API endpoint, response format with possible error codes, fixed currency (RUR), and rate limits. This adds far more than the annotations (readOnlyHint=false, idempotentHint=true) and leaves no ambiguity about side effects or limits.

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 concise and front-loaded: states the primary action and batch size first, then response format, error codes, and rate limits in a compact sequence. Every sentence adds value without redundancy or filler.

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?

Given the tool's complexity and absence of an output schema, the description fully covers necessary behavioral context: what to expect in the response, possible error codes, rate limits, and how to handle large batches. No critical gaps remain.

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?

With 100% schema description coverage for the single 'offers' parameter, the schema already fully explains parameter semantics. The description does not add significant parameter-specific detail beyond what the schema provides; it only reiterates currency and batch limits.

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 explicitly states the tool's purpose: 'Массово обновляет цены' (massively updates prices) and specifies the batch size (1–2000 offers per request). This clearly differentiates it from sibling tools like set_offer_price (single offer) or set_offer_discount (discounts).

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?

The description provides concrete usage context: batch quoting, rate limit (50,000 changes/min), and guidance to split large volumes into multiple calls. It does not explicitly name alternative tools but implies batch-only use, which is clear from sibling names.

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