uber_eats_remove_from_cart

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

No annotations are provided, so the description carries the burden. 'Remove' clearly signals a mutating destructive action, but the description doesn't disclose specifics like what happens if the item isn't in the cart, whether quantity matters (does it remove all or one?), or if confirmation is needed. The mutation is implied correctly but thin on detail.

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?

Extremely concise - one sentence for the purpose and a single-line parameter description. No wasted words, front-loaded with the core action.

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?

This is a mutating cart operation with no annotations and 0% schema coverage, so the description carries full burden. It fails to cover behavioral edge cases: what happens with quantity (removes entirely vs one instance), behavior for non-existent items, and interaction with add_to_cart/update_cart_quantity semantics. For a destructive cart mutation, this is insufficiently specified.

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%, so the description must compensate. It states 'Name of the item to remove' which matches the schema's declared 'item_name' param, but adds no additional semantics like case sensitivity, whether exact name matching is required, or how the name should be obtained (e.g., from view_cart results). Table stakes only.

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 'Remove an item from the cart by name' - specific verb+resource with the removal mechanism (by name). This distinguishes it from sibling tools like add_to_cart, update_cart_quantity, and view_cart, though it doesn't explicitly reference them.

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 action is simple and self-explanatory for when to use it (removing from cart), but there's no explicit guidance on when NOT to use it or interactions with related tools like update_cart_quantity. No mention of prerequisites such as needing an active cart or logged-in session.

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