meican_list_meal_tabs

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

With no annotations, the description carries full burden. It discloses that each tab has a deadline (target_time) and that existing_order indicates a prior order. It advises to surface existing orders instead of placing duplicates. No destructive behavior is implied; the tool is read-only. The description adequately informs agent behavior.

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?

Three sentences, each earning its place: first defines purpose, second explains key fields and usage, third gives ordering guidance. Front-loaded with the core action. No verbose or redundant 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?

No output schema exists, so the description should outline return value structure. It mentions tab_unique_id and target_time, implying a list of objects, but does not fully describe the response format (e.g., array, additional fields like existing_order). However, the core information needed for a simple list tool is present.

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 coverage is 100%, so baseline is 3. The description adds context that target_time is the order deadline and should be passed verbatim, but this is not substantial beyond the schema's own descriptions. No additional parameter meaning is provided.

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?

Clearly states the tool lists meal sessions (餐次) for a given date, with specific examples like 午餐, 晚餐. Distinguishes itself from sibling tools by positioning as the first step for ordering or viewing orders, with explicit mention of tab_unique_id and target_time for use in subsequent tools.

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?

Explicitly says 'Use this FIRST when the user wants to order or view orders for a day.' Provides guidance on handling existing_order to avoid duplicates. While it doesn't list alternatives, the context is clear enough for an agent to decide when to invoke this tool.

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