rami_levy_add_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure and delivers exceptionally: immediate whole-cart sync to the real account, additive qty semantics, rejection behavior (items removed from cart), the ok:false transport meaning 'nothing changed,' and the resetAfterOrder edge case where prior items are cleared as bought. It even tells the agent what to communicate to the user in each failure and reset scenario.

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?

Every sentence earns its place — the transport-vs-items_rejected error modes and resetAfterOrder edge case are dense but necessary given the tool's complexity. However, it is a single unbroken paragraph of roughly 150 words; light structural breaks would improve scannability, though information density is high and no filler exists.

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?

Despite having no annotations and no output schema, the description fully covers input provenance, return values (cartTotal estimate vs authoritative serverTotal), both error modes with prescribed agent actions, and the post-order cart-reset scenario with explicit user-facing instructions. An agent could invoke this tool safely and handle every documented outcome with no additional information.

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 compensate, and it contributes the most critical semantic: all three required parameters must come verbatim from a prior search result, never guessed or re-fetched. It also explains qty as additive rather than overwriting. It stops short of specifying qty's default value or price's currency/units, leaving the 0%-coverage schema not fully compensated.

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 opening sentence, 'Add a product to the shared cart,' names a specific verb and resource, immediately distinguishing it from siblings like rami_levy_remove_item, rami_levy_clear_cart, and rami_levy_view_cart. The action ('add') and scope ('shared cart') leave no ambiguity about the tool's function.

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 explicitly binds the tool to an upstream workflow: 'productId, name, and price all come from a prior rami_levy_search_products result — never guessed, and never re-fetched,' and it clarifies the duplicate-product rule (qty is ADDED, not overwritten). However, it never explicitly names sibling alternatives or states when NOT to use this tool, leaving some differentiation to inference.

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