update_price

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

No annotations are provided, so the description must fully disclose behavior. It labels the tool as a 'guarded write' implying destructive action but does not explain what happens on success/failure, rate limits, authentication requirements, or any side effects. This is insufficient for a write operation with zero annotation support.

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 sentences, front-loaded with '[Catalog / guarded write]' for quick classification. Efficient but could include brief behavioral notes without becoming verbose.

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 is present, yet the description does not explain return values or error handling for a write tool. Critical details like response format or confirmation of price update are missing, making it incomplete for agent use.

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 parameter descriptions. However, the tool description adds no additional meaning beyond the schema—e.g., what format the 'changes' array should have or how 'preview' vs 'dry_run' interact. Baseline 3 is appropriate as the schema does the heavy lifting.

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 submits listing price updates via the Listings Items API, specifically a guarded write for catalog operations. It distinguishes itself from sibling update tools like update_listing by focusing solely on price updates.

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 mentions it is a hosted endpoint only and that this local server is an introspection stub, providing context that it may not be functional locally. However, it does not explicitly state when to use this tool versus alternatives like update_listing or other update tools.

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