shakeshack_menu

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

No annotations are provided, so the description carries the full burden. It discloses a critical behavioral quirk: many items price through a required size selection rather than a base price, so price is commonly 0 for those items. This is exactly the kind of non-obvious behavior an agent needs to know to interpret results correctly. It also describes the return structure (category tree with products, customization tree, etc.). It doesn't mention rate limits or auth, but for a read-only menu fetch, the disclosed pricing quirk is the most important behavioral detail.

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, information-dense paragraph. It front-loads the core purpose and then details the return structure and the pricing quirk. Every sentence adds value: the return structure, the badge examples, the customization tree, and the pricing behavior. It's slightly long but justified given the complexity of the menu data. No wasted words.

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 single-parameter read-only tool with no output schema, the description is quite complete. It explains the return format (category tree), the fields included (name, description, calories, allergens, badges, image, customization tree), and the non-obvious pricing behavior. The only gap is that it doesn't explicitly state whether the response includes all locations or just one, but the first sentence makes 'one location' clear. It also doesn't mention pagination, but for a full menu that's likely unnecessary.

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% and the single parameter location_id is described in the schema as 'Location id from /shakeshack/nearby'. The description reinforces this by stating where location_id comes from. With only one parameter and full schema coverage, the description adds marginal value by repeating the source, but the baseline for high coverage is 3; the description's explicit mention of the source endpoint adds a small increment, making it a 4.

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 opens with a specific verb and resource: 'Get one Shake Shack location's full menu.' It clearly distinguishes this from sibling tools like shakeshack_locations, shakeshack_nearby, and shakeshack_store by focusing on the menu retrieval. The scope is explicit: one location's full menu, returned as a category tree.

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 states that location_id comes from GET /shakeshack/nearby, which provides clear context on how to obtain the required parameter. It doesn't explicitly name alternative tools or state when not to use this tool, but the context of needing a location_id from nearby is sufficient guidance for an agent. The sibling list includes shakeshack_locations, shakeshack_nearby, and shakeshack_store, but the description doesn't explicitly contrast with them.

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