get_ubereats_order_details

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

With no annotations, the description carries the behavioral disclosure burden. It does this well by specifying what is returned, noting the receipt is included by default, and naming the card-brand/last-4/time details. It does not explicitly state side effects or error behavior, but the operation is clearly a read-only detail fetch.

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 a single dense sentence that front-loads the purpose and then lists contents in a colon-separated list. Every clause earns its place, though the sentence is slightly overloaded with detail.

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?

Given two simple parameters and no output schema, the description provides a thorough account of what the call returns, including default receipt behavior. Minor gaps remain around what happens when include_receipt is false and any prerequisite auth state, but the definition is largely self-sufficient.

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 100%, so the schema already documents both parameters. The description adds only minor semantic reinforcement by confirming the receipt is included by default, matching the include_receipt default.

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 identifies the resource ('one Uber Eats order') and enumerates the returned categories: items, fare breakdown, receipt charges, tips, refunds, and addresses. It is distinguishable from sibling tools by its singular-order scope, though it doesn't explicitly name an alternative.

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 implies this is the tool for fetching details about a specific order, and the schema adds context that the order_id comes from get_ubereats_orders. However, it does not explicitly explain when to choose this over get_ubereats_transactions or get_ubereats_orders, leaving routing largely to inference.

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