get_ubereats_menu

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

With no annotations provided, the description carries the full burden and succeeds: it reveals that the tool scrapes live network data at call time, requires internet access, depends on store location/hours, and returns an empty result rather than an error for invalid/unavailable/empty menus. These are crucial behavioral traits that go beyond the schema.

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 three dense sentences, each earning its place: the first states purpose and output, the second explains live scraping behavior, and the third covers edge cases. It is front-loaded with the primary action and contains no filler.

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 the tool's simple single-parameter interface, the presence of an output schema, and no annotations, the description covers all necessary context: what it returns, how it behaves at runtime, and failure modes. It is complete enough for an agent to select and invoke the tool correctly.

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?

The parameter store_url is fully documented in the schema, including its source (search_ubereats result) and an example. Since schema description coverage is 100%, the baseline is 3, and the main description adds no additional parameter-level 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 opens with a specific verb ('Fetch') and resource ('an Uber Eats restaurant's live menu from its store URL'), immediately distinguishing it from generic scrapers like scrape_url and from search_ubereats. It also specifies the key output fields (names, descriptions, prices), leaving no ambiguity about what the tool does.

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 the tool is for store URLs (especially from search_ubereats, as noted in the schema) but does not explicitly state when to use it over sibling tools like scrape_with or scrape_url. It gives context about needing a valid store URL and network access but stops short of clear when-to-use/when-not-to-use guidance.

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