cart_add_configured

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description usefully adds that the cart must be empty, that it runs once, that it does not order or pay, and that checkout_quote is next. It does not explain what happens if the empty-cart precondition is violated.

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?

Three compact sentences with the main constraint and next step front-loaded. Every sentence adds useful operational context without repetition.

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?

The description gives enough high-level workflow context for selection and sequencing, and annotations cover the safety/idempotency profile. However, for a mutation tool with a complex required request object and no output schema, it omits important request-field semantics.

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 description coverage is 0%, so the description must carry parameter meaning. It partially explains item selection via live offer_id and combo round/items, but it does not explain the required request object fields (account, store_code, pickup_at, max_amount_cny, eat_type) or the idempotency_key.

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?

States a specific verb and resource: add selected items/combos to an EMPTY cart once. It references product_detail and checkout_quote, but does not explicitly distinguish this configured variant from the sibling cart_add_simple.

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?

Gives clear usage context: use live offer_id and explicit round/items choices from product_detail, only standard modifiers, and call checkout_quote next. It lacks explicit when-not guidance, such as what to do for a non-empty cart or when cart_add_simple is more appropriate.

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