uber_eats_set_checkout_payment

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

No annotations are provided, so the description carries the burden. It names the underlying API mechanism (PATCH payments profilePatch) for set_as_default, which is useful credential/behavioral context. However, it doesn't disclose whether setting payment is destructive/irreversible, what happens to previously selected payment, rate limits, or auth requirements. The mention of 'toggles Uber Cash/credits' and side-effect behavior of set_as_default adds meaningful behavioral 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?

The description is reasonably compact with effective use of an Args block for parameter clarification. It's front-loaded with the primary purpose, then tapers to parameter details. Slightly verbose with the 'payments profilePatch' internal detail embedded mid-sentence, but every sentence earns its place in explaining behavior and parameter semantics.

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?

With an output schema present, the return-value burden is reduced. The description covers dependencies (draft from preview, payment profiles from list tool), optional behavior (credits toggle, default persistence), and side effects (PATCHing account default). Given the medium complexity of 4 params with undocumented schema coverage, the description fills the gap adequately.

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 fully compensates for parameter semantics. It explains each parameter's role: use_credits 'If true or false, toggles Uber Cash/credits; empty leaves unchanged', set_as_default 'persist as default payment on the selected Uber profile'. It correctly documents the empty-string default behavior that would otherwise be ambiguous given the schema's default of ''.

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 tool 'Select payment method for checkout (API)' with specific verb+resource. It distinguishes from siblings by referencing the payment methods list tool and the checkout flow (draft_order_uuid from checkout preview, payment profile from list_payment_methods), situating it precisely in the checkout sequence among many similar 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 provides clear sources for parameter values (payment UUIDs from uber_eats_list_payment_methods, draft_order_uuid from checkout preview), which acts as when-to-use guidance within the checkout pipeline. It doesn't explicitly state when NOT to use it or name alternatives, but the integration context with sibling tools is strongly implied and sufficient.

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