⚠️ Применить услуги VAS

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

Annotations already indicate destructiveHint=true, and the description reinforces the cost aspect. The description does not disclose other behaviors like idempotency (despite the idempotencyKey parameter being documented in the schema). The parameter dryRun provides a safe preview, but this is in the schema, not the description.

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?

Single sentence with emoji warning is concise. Could be improved by separating the cost warning from the action, but it is efficient.

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?

No output schema and description does not mention return value, success indication, or cost details. For a paid destructive action, this is insufficient. Also lacks prerequisites like having an existing ad or sufficient balance.

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 parameters with descriptions (100% coverage). The main description only lists slugs and stickers generically, adding no new meaning beyond what the schema already provides.

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 applies promotion services (slugs) and/or stickers to one ad (verb+resource). It mentions 'several' but does not explicitly distinguish from sibling tool items_put_item_vas which likely applies a single 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?

Description warns that it is paid and spends money, which is useful. However, it does not provide when to use vs. alternatives like items_put_item_vas or the package version, nor does it state prerequisites.

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