toast_list_dining_options

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

With no annotations, the description carries the full behavioral burden, but it only says 'List all dining options.' This implies a read-only operation, yet it does not explain whether results are restaurant-scoped, whether restaurantGuid is needed, or what the response shape looks like. The description adds little beyond the tool name.

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, efficient sentence with no filler and is front-loaded with the action. It is concise, though its brevity contributes to the lack of context. Still, for pure conciseness and structure, it earns a solid score.

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?

For a tool with one undocumented parameter and no output schema, the description is incomplete. It does not explain the optional restaurantGuid parameter, whether the list is global or scoped, or what will be returned. An agent cannot confidently know how to invoke this tool for a specific restaurant even though the name suggests restaurant context.

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% and the only parameter, restaurantGuid, has an empty description. The tool description never mentions this parameter, so the agent has no information about how or why to use it. There is no compensating semantic guidance.

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 uses a specific verb and resource: 'List all dining options' and enumerates examples like dine-in, takeout, delivery, and curbside. This makes the tool's purpose clear and distinguishes it from sibling menu-related tools, though it does not explicitly contrast with any alternative tool.

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?

No guidance is given about when to use this tool versus sibling tools such as toast_get_delivery_settings or toast_list_menus. The description only states what the tool does, leaving the agent to infer usage context without any exclusions or alternative routing.

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