shangou_shop_menu

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

No annotations provided, so description carries full burden. It mentions the tool returns dish names and prices and that parsing is 'best effort', which is a useful behavioral trait. However, it does not disclose read-only nature or other typical constraints.

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 with no redundant information. Every part contributes: purpose, parameter format, output description. Extremely concise and front-loaded.

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?

Despite lacking output schema, description adequately states that output includes dish names and prices with a caveat. For a simple list tool with two params, it covers essential information. Minor missing details like pagination or error handling, but overall 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?

Schema description coverage is 100%, and the description reiterates the same parameter explanations (shop as ID or URL, limit as count). It adds Chinese translation but no new semantic depth beyond 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?

Description clearly states the tool retrieves a store's menu/products (查看某店铺的菜单/商品), which is a specific verb+resource. It distinguishes from sibling tools like shangou_add_to_cart or shangou_search.

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?

Description explains how to use parameters (shop and limit) but does not provide when-to-use or when-not-to-use guidance, nor alternatives. Context signals show siblings, but no explicit usage context.

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