get_restaurant_item_details

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

The description adds behavioral context beyond annotations: it explains the output contains nested customization groups (extras with options), and clarifies a prerequisite for cart addition. The annotations (readOnlyHint, openWorldHint, destructiveHint) are consistent and the description complements them well.

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 a single paragraph of three sentences, each earning its place: purpose, prerequisite, and usage instruction. Information is front-loaded with the core output details first. No redundant or unnecessary 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?

Given 4 required params and no output schema, the description provides adequate context: what is returned (price, description, extras with options), when to use (required before adding items with modifiers), and how to use the output. Minor missing details like error handling do not detract significantly.

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 the baseline is 3. The description does not add significant parameter-level details beyond the schema; it focuses on the overall output and usage. No contradiction or omission regarding parameters.

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 clearly states the tool returns full details for a restaurant menu item including price, description, and extras customization groups. It distinguishes from sibling tools like get_menu and add_items_to_cart by specifying its role as a prerequisite and detailing the output structure.

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 states when to use this tool: REQUIRED before adding any item with has_required_modifiers. Provides specific instructions on how to use the returned data: pass options[].option_id as nested_options when adding to cart, and notes never to use extra_id.

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