Перезапись корзины

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

The description adds substantial behavioral detail beyond annotations: absolute quantity semantics, full-cart rewrite behavior, countAvailable rejection with CART_QUANTITY_CONFLICT, no silent clamping, and the post-change cart return value. No contradiction with annotations is present.

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 compact for its complexity, well-structured with line breaks, and each sentence adds functional value. It front-loads the key distinction from grocery_add_to_cart and does not repeat schema fields.

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 the output schema exists, return-value description is optional, but the tool still explains the post-change contents. Error behavior, full-rewrite mechanics, absolute semantics, and parameter semantics are all covered, making this complete for correct invocation.

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 schema has no parameter descriptions, but the description compensates well: items gets a JSON structure with count>0, count=0, and omitted-item semantics, and clear gets an explanation. app_id and point_id are not individually explained but are clear identifiers and optional with defaults.

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's action: modify or remove cart items by overwriting quantities. It explicitly distinguishes itself from grocery_add_to_cart, which increments quantities, so an agent can tell it apart without opening the schema.

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 explains exactly when to use this tool vs grocery_add_to_cart, how count=0 removes items, how items omitted stay untouched, and how clear=True empties the cart. It also clarifies that there is no dedicated delete endpoint, so the tool must rewrite the whole cart.

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