⚠️ Apply VAS package

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

Annotations already indicate destructive, but description adds critical context: charges money irreversibly, response includes charged amount, and errors may not mean failure. No annotation contradictions.

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?

Description is compact yet informative, with warnings and contrasts front-loaded. Every sentence adds value, though minor restructuring could improve readability.

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 covers purpose, differentiation, prerequisites, error handling, and deprecation. Missing details on success effects beyond charged amount, but sufficient for a well-informed call.

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 coverage is 100% with parameter descriptions, so description adds only the context that package_id comes from items_post_vas_prices. This is useful but not essential; baseline 3 is appropriate.

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 applies a VAS package to a listing, explicitly contrasting it with sibling tools items_put_item_vas (single service) and items_apply_vas (arbitrary set). It also notes deprecation and the recommended replacement.

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?

Provides explicit when-to-use guidance (pre-assembled package), distinguishes from alternatives, gives prerequisite (check price via items_post_vas_prices, confirm with user), and warns about error handling (verify purchase if error).

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