Change a listing price

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

The description adds valuable behavioral context by noting that favourited buyers are notified of price drops, which is not captured in annotations. It also includes the confirmation requirement. This goes beyond what annotations already provide.

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 with no fluff. The core action is front-loaded, and the caveat about notifications is included efficiently.

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, the description covers the main function and a key side effect, but lacks parameter details and does not address potential confusion with edit_listing, leaving some gaps for an agent.

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?

The description does not explain the itemId or price parameters, and with only 25% schema description coverage, it fails to compensate for undocumented parameters like currency and country. It only implies that itemId refers to a live listing.

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 changes the price of a user's live listing, using a specific verb and resource. This distinguishes it from sibling tools like edit_listing or draft management tools.

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?

It instructs to confirm the new price with the user first, which is useful context. However, it does not explicitly mention when to use this tool over alternatives like edit_listing for broader changes, leaving usage somewhat implied.

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