update_store_cart

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

With no annotations, description covers important behaviors: returns 404 for invalid IDs, max 10 concurrent requests, respects read-only/dry-run modes, and line items must be fully replaced. Adequately compensates for lack of annotations.

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?

Structured with paragraphs and Args list, front-loaded with main action. Returns section is slightly redundant given output schema but not harmful. Efficient for 7 parameters.

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 7 parameters, no annotations, and output schema provided, description covers update behavior, line item replacement, error cases, auth, rate limits, and dry-run. Completeness is high.

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?

Since schema description coverage is 0%, description lists and explains all 7 parameters, adding context like 'ISO 4217 currency code' and 'JSON string with replacement line items array'. Provides more than schema titles. Could add type constraints or example formats.

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?

Description clearly states the specific verb (update) and resource (existing cart), listing the fields that can be updated: totals, currency, checkout URL, or line items. It distinguishes from sibling tools like 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?

Provides explicit guidance: 'Only provided fields are changed' and explains that line items require full replacement via lines_json (partial updates not supported, suggesting alternative). Mentions auth and rate limits. Could include when to use other cart tools like delete or get.

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