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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: the data composition (what fields exist), the explicit absence of prices, and the join key (item_id) required to combine with menu tools. It doesn't mention pagination, caching, or rate limits, keeping it below a 5.

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 tight sentences with zero filler. The contents enumeration is front-loaded and the join/routing constraint is placed second where it is immediately actionable. Every clause earns its place.

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?

An output schema exists, so return-value explanation is unnecessary. The description covers what data the tool returns, the join key, and the missing-prices caveat, which is sufficient for an agent to use it correctly. It could have noted that region/channel alter the returned catalog, but this is a minor gap.

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% with only two optional parameters (region, channel), each documented in the schema with defaults. The description adds no parameter-level detail, so the schema carries the full burden and baseline 3 applies.

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?

States a specific resource (Chipotle menu presentation metadata) and enumerates its exact contents: nav categories with imagery, per-item nutrition, dietary tag codes, customization pick-groups, and the tag taxonomy. It distinguishes itself from siblings by explicitly noting the absence of prices and pointing to chipotle_menu/chipotle_restaurant_menu as the price-bearing 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?

Gives clear routing guidance: 'No prices -- join on item_id against chipotle_menu or chipotle_restaurant_menu', which tells the agent both what this tool is for and which siblings to combine it with. It stops short of stating explicit when-not conditions (e.g., 'use this only when you need nutrition/tag data'), so it's clear context without full exclusion logic.

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