get_ubereats_orders

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

With no annotations, the description must carry behavioral disclosure. It does add useful behavior: source is Uber Eats' order-history feed, pagination stops after start_date, and include_receipts triggers one extra call per order. It does not mention authentication, rate limits, or error behavior, which are notable gaps but not fatal.

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?

Three dense sentences with no wasted words. The purpose is front-loaded, followed by paging behavior and the optional receipt parameter. Every sentence contributes useful information.

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 no output schema, the description compensates by listing the returned fields, paging behavior, and the receipt-expansion option. It omits auth concerns and does not explain max_pages/end_date interaction, but those are partially covered by the schema and this is a read-only list operation.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds a small amount of meaning around include_receipts and paging past start_date, but it does not substantially enrich parameter semantics beyond what the schema already provides.

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 names a specific verb and resource ('List Uber Eats orders'), the ordering ('newest-first'), and the exact returned data (items, fare breakdown). It is clear enough to distinguish from siblings like get_ubereats_order_details and get_ubereats_transactions, though it does not explicitly name 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 description gives clear context for when this tool is appropriate: it is the order-history feed and optionally fetches receipts. However, it never states when to use an alternative such as get_ubereats_order_details or get_ubereats_transactions, so the boundary to related tools is left to inference.

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