Установить скидку на товар

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses critical behavioral details: client-side validation of the discount range (5–95%), fixed currency (RUR), and the exact API response shape. This adds significant context beyond 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?

The description is compact (3 sentences) and front-loaded with the primary action, followed by endpoint context, validation, currency, and response format. Every sentence contributes unique information with no redundancy.

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 absence of an output schema and the presence of four required parameters, the description is remarkably complete: it covers validation, currency, response format, and the distinction from sibling tools. An agent can confidently invoke this tool correctly based on the description alone.

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 input schema already provides comprehensive per-parameter descriptions (100% coverage). The description adds the relationship between price and discount_base (the 5–95% rule) and reinforces the required nature of discount_base, providing extra semantic value beyond the schema.

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 clearly states the tool's function ('Устанавливает скидку') and precisely defines the roles of price and discount_base. It further distinguishes itself from sibling tools by noting it uses the same POST endpoint but requires discount_base, making it the dedicated discount-setting tool.

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 implies usage for setting discounts with a mandatory discount_base, contrasting with sibling tools like set_offer_price and update_offer_prices. It also provides validation rules (5–95%) and currency constraints, giving clear context for when the tool is appropriate, though it does not explicitly name alternative tools for non-discount price updates.

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