rami_levy_add_item

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

With no annotations, the description fully carries the behavioral burden. It discloses additive qty semantics, immediate sync to the real Rami Levy account, the distinction between local cartTotal and authoritative serverTotal, and the exact meaning of ok:false, transport failure, and items_rejected. No contradiction exists.

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 dense but every sentence earns its place: purpose, input sourcing rule, qty semantics, sync behavior, return values, and error handling. The most important constraint is front-loaded immediately after the purpose statement.

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?

For a mutation tool with no annotations and no output schema, this is unusually complete. It explains side effects (cart sync, product removal on rejection), return values (cartTotal, serverTotal), and failure modes, so an agent has enough information to invoke it correctly and handle outcomes.

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?

Despite 0% schema description coverage, the description compensates richly: productId, name, and price are tied to a prior search result, and qty is defined as additive rather than overwriting. This gives the agent more semantic meaning than the raw schema alone.

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 opens with a specific verb and resource: 'Add a product to the shared cart.' It also distinguishes itself from the search flow by stating inputs must come from a prior rami_levy_search_products result and that no 'get one product' endpoint exists, so an agent can tell it apart from sibling tools.

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 gives clear usage context: productId, name, and price must come from a prior search result and must never be guessed or re-fetched. It does not explicitly compare itself to alternatives like remove_item or reorder_from_history, but for an add-item operation this is strong enough guidance.

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