Изменить цену предложения

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

Beyond annotations, it discloses auto-inserted currency, discount percentage validation leading to HTTP 400, strict pairing requirement for special-price fields, exact API response format, side effect on duplicate IDs (only first updated), and rate limit of 50k changes/minute. No contradiction with annotations.

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?

Every sentence contributes new, actionable information: scope, currency, optional fields with validation, response format, duplicate handling, and rate limit. No redundant or filler content.

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 no output schema, the description fully explains the API response (status OK or ERROR with errors array), and covers edge cases (duplicate IDs) and operational limits (rate). Together with the parameter constraints, it provides a complete operational picture for an agent.

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 covers all 6 parameters at 100%, but description adds valuable cross-parameter context: currency always RUR, discount_base must be > price and within 5–95%, and pay_by_price/pay_by_condition are mutually required. This supplements the schema meaningfully.

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?

Description clearly states it changes the price of a single product offer, specifying the exact endpoint (POST /offer-prices/updates) and the singular scope. This distinguishes it from sibling batch tools like update_offer_prices.

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?

Explicitly notes this is for one element and introduces optional parameter constraints (discount_base + pay_by_price/condition), plus duplicate-ID behavior and rate limit. However, it does not directly name the batch alternative, only implies it via 'c одним элементом'.

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