uber_eats_checkout_savings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It notes '(API)' and 'Requires a non-empty cart' but doesn't state what happens if the cart is empty (error?), whether this is a read-only operation, or anything about the response structure despite an output schema existing. For a tool with zero annotation coverage, more behavioral context is needed.

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?

Two short sentences that are front-loaded with the core purpose. The second sentence adds the prerequisite. No wasted words, though slightly more detail could be included.

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?

There is an output schema present, so return values need not be explained in the description. The tool is a simple no-parameter fetch operation, so the description covers the essentials: what it does and a key precondition. However, given no annotations and the absence of guidance on error/empty-cart behavior, it's somewhat thin.

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?

With 0 parameters, there's nothing for the tool to document, and schema description coverage is 100%. The baseline is 4 for zero parameters. The description adds context that it operates on the 'current draft order' which is useful beyond the empty schema.

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 it fetches checkout savings/promo carousel data for the current draft order. The verb 'fetch' plus resource 'checkout savings / promo carousel data' is specific. It also distinguishes from siblings like uber_eats_apply_promo (which applies a promo) and uber_eats_checkout_preview (which previews checkout).

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 requirement 'Requires a non-empty cart' provides a clear precondition for when to use this tool. However, it doesn't explicitly state when NOT to use it or name alternatives. Given siblings like uber_eats_apply_promo, the distinction is implied but not explicit.

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