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

No annotations are provided, so the description carries the full burden. It does useful work — disclosing that prices are pre-tax and describing mode-dependent return content (name, description, price or size prices) — but it says nothing about permissions, behavior for an unrecognized section name, or whether results are cached/live, which matters for a tool with no safety annotations at all.

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?

Dense, front-loaded prose in four short clauses, each tied to a distinct calling mode; zero filler and the offer/price caveat is folded in without bloating the text.

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 two optional params, no nesting, and no output schema, the description covers what an agent needs: the three modes and the shape of what comes back. Minor gaps (unrecognized-section behavior, relationship to search_menu) keep it from being fully complete.

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%, and the schema already enumerates example section names and explains the vegetarian/gluten_free kitchen-marker caveat, so the baseline is 3. The description restates the dietary filter's effect ('only items carrying that marker') without adding syntax or nuance beyond the 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 states the resource (menu with USD prices) and precisely describes the three calling modes (no args = overview, section = items, dietary = filtered items) plus what each returns. It's clear enough to call correctly, but it never contrasts itself with the sibling search_menu, which is the main ambiguity an agent would face.

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?

It explicitly maps each parameter combination to an outcome: no arguments gives a menus/sections overview, section gives items, dietary restricts to marked items — effectively telling the agent when to use each form. What's missing is guidance on when to prefer this over search_menu, so an agent with no section name in mind still has to guess.

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