update_item_price

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

The description adds a valuable behavioral directive by requiring confirmation before applying the change. However, with no annotations, it does not disclose other behavioral traits such as reversibility, authorization needs, or side effects on historical data.

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 two sentences, front-loaded with the primary purpose, and includes actionable trigger phrases and a confirmation requirement. Every sentence earns its place with no unnecessary 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?

For a simple price update tool with two well-described parameters, the description covers when to use, what it does, and the confirmation step. However, it lacks information about return values or error handling, which could be relevant given the absence of an output schema.

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?

Both parameters are fully described in the schema (item_code and new_price in Ariary). The tool description adds no additional parameter semantics beyond what the schema already provides, so the 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 action: updating a product's selling price. It provides specific trigger phrases and distinguishes this tool from stock-related siblings like adjust_stock.

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?

Explicit usage criteria are given with trigger phrases, and the confirmation step is a clear behavioral instruction. However, it does not mention when not to use this tool or suggest alternative tools, so it lacks exclusions or alternatives.

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