menu_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one valuable trait — that displayed prices are not final quotes — but discloses nothing else about what a 'live' menu returns or why a checkout-shaped request is required.

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 short sentences with the scope front-loaded and no padding. It is efficient, though the terse framing borders on under-specification for a tool with a required nested request object.

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, no parameter descriptions, and a required checkout-like request object unexplained, the description does not give an agent enough to call the tool correctly. The complexity signaled by the schema is not matched by the description.

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 0%: neither 'keyword' nor the nested 'request' object's fields (account, store_code, pickup_at, max_amount_cny, eat_type) carry any description, and the tool description mentions no parameters at all. Given four required sub-fields on a required object, this leaves the agent guessing at their meaning and format.

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?

States a specific verb and resource ('Browse a live store/time menu') plus a notable inclusion ('card offers'), so an agent knows it returns menu content. It does not contrast with siblings like product_detail or store_get, so differentiation is left implicit.

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 no when-to-use or when-not-to-use guidance and names no alternative. An agent cannot infer from the text whether to call this versus product_detail or checkout_quote for pricing.

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