⚠️ Change price

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

Description adds behavioral context beyond annotations: price is immediately visible to buyers (open world detail), no money spent, rate limit 150 req/min. It also notes this is a live change, confirming destructiveHint. 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?

Extremely concise: two sentences plus a parenthesis. Front-loaded with purpose, followed by key constraints. No superfluous words.

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, description covers impact (public visibility), rate limit, category restrictions, and user confirmation. Missing details on dryRun preview, but overall sufficiently complete for a simple mutation tool.

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 good descriptions. Description reiterates required params (item_id, price as integer in rubles) but adds no new semantic value beyond what schema already provides. Baseline of 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 changes a listing's price, using a specific verb ('Changes') and resource ('listing's price'). It distinguishes itself from sibling tools (e.g., items_get_item_info, items_apply_vas) by focusing on price modification only.

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 provides clear when-to-use context: requires item_id and price, specifies allowed categories (with explicit exclusion), and advises user confirmation for live changes. It does not explicitly contrast with alternatives, but no direct sibling for price update exists.

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