⚠️ Применить VAS

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

Annotations include destructiveHint=true, and the description adds emphasis on payment ('ПЛАТНОЕ', 'тратит деньги с баланса'). Also explains dryRun and idempotencyKey behavior, adding value 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?

Two concise sentences, front-loaded with a warning symbol and 'ПЛАТНОЕ'. Every sentence adds value without 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?

Covers the essential paid nature, prerequisite call, and dryRun safety. Could be more complete by mentioning error conditions like insufficient balance, but overall adequate for a mutation tool with good annotations.

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 100%, so baseline is 3. The description provides example vas_id slugs but does not add significant meaning beyond the schema's parameter descriptions.

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 it applies a single VAS to an item and costs money, using the vas_id slug. It distinguishes from the prerequisite tool items_post_vas_prices but does not explicitly differentiate from the similar sibling items_apply_vas.

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 instructs to call items_post_vas_prices first, providing a clear prerequisite. Also notes the dryRun parameter for safe preview. No guidance on when not to use or comparison to other VAS tools.

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