uber_eats_saved_addresses

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

No annotations are provided, so the description carries full burden. It conveys it's a read-only list operation (implied, not explicit), mentions that addresses are labeled, and reveals what kind of data is returned. It doesn't state details like auth requirements, whether this returns default addresses, or format specifics, but given the low complexity it's reasonably adequate.

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 sentences, zero waste. The description front-loads the core purpose in the first sentence and adds the actionable next step in the second. Every word earns its place.

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?

For a zero-parameter list tool with an output schema present, the description covers the essential use case well. It explains the purpose and points to the related tool for switching. Given the tool's simplicity and the presence of an output schema, this level of description is 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?

There are zero parameters, and schema coverage is 100%. With no params, the baseline of 4 applies. The description adds meaningful context about what's returned (labeled addresses) that supplements 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 uses a specific verb ('List') with a clear resource ('all saved delivery addresses') and explains what it returns (labeled addresses like home, work). It distinguishes from sibling uber_eats_get_address implicitly, though it doesn't explicitly contrast with it or other sibling tools like uber_eats_search_history.

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 usage context — it lists all saved addresses and explicitly directs the user to use uber_eats_switch_address to switch between them. This names the relevant next-step alternative. However, it doesn't explicitly state when NOT to use this tool or contrast with uber_eats_get_address.

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