uber_eats_add_to_cart

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

No annotations are provided, so the description carries the full burden. It discloses important behavior: the server auto-resolves section/subsection UUIDs, fixes wrong search data automatically, and uses fuzzy matching on the fallback path. It does not describe auth requirements or what happens on failure, but the behavioral disclosure is substantial for the mutation context.

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 clear priority sections (Best/Optional/Fallback) and bullet-point args. Slightly long but every sentence adds value—the implementation details (addItemsToDraftOrderV2, getMenuItemV1, getStoreV1) and the 'never the same as store_uuid' warning are genuinely useful, not filler.

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 no annotations, the description covers the complex 7-parameter multi-path API thoroughly: priority resolution, auto-fix behavior, customization prerequisite, and parameter relationships. With an output schema present, lack of return-value explanation is acceptable. Could mention error cases or payment requirements, but the core execution flow is well covered.

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 coverage is 0% with 7 parameters, so the description must fully compensate—and it does. Each parameter gets a meaningful explanation (e.g., 'section_uuid: Catalog section UUID (never the same as store_uuid; optional if resolvable from menu)'), adding relationships, defaults, and usage conditions beyond what the bare schema titles provide.

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 clearly states the verb+resource ('Add a line via addItemsToDraftOrderV2 + getMenuItemV1') and covers both restaurant and grocery contexts. It differentiates from siblings like uber_eats_remove_from_cart and uber_eats_update_cart_quantity by focusing on adding a new line item.

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 priority guidance: best path (store_uuid + menu_item_uuid), optional fields, and fallback (restaurant_url + item_name). Explicitly instructs when to call uber_eats_get_item_options first for required customizations. Includes the critical warning that section_uuid is never the same as store_uuid.

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