update_store_cart

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

Annotations are all false. Description adds operational details: mutation behavior, partial update for non-line fields, and error response. Does not contradict annotations. Could mention idempotency or side effects.

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?

Well-structured with Args and Returns sections, uses bullet points, and is efficient. Minor redundancy with schema but overall clear and focused.

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?

Covers all parameters, return fields, and error condition. Missing details like rate limits or authentication, but given no output schema, return info is helpful. Adequate for a relatively simple update operation.

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?

With 0% schema description coverage, the description compensates fully by listing all parameters with clear, concise explanations, including the special behavior for lines_json.

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?

Clearly states the tool updates an existing cart, lists specific updatable fields (totals, currency, checkout URL, line items). Distinct from sibling create_store_cart and delete_store_cart.

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?

Explicitly notes that only provided fields change and that partial line-item updates are not supported, guiding users to alternative methods. Mentions 404 error for invalid IDs. Lacks explicit comparison to other tools but provides clear context.

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