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 usefully adds what content is returned (sourcing story, imagery, menu-item linkage, recipe breakdown), but says nothing about pagination, rate limits, or how the recipe breakdown relates to the ingredients catalog.

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?

A single dense sentence with the resource and its contents front-loaded and no filler. It is appropriately sized, though the compound 'plus the per-item recipe breakdown' clause packs two distinct return shapes into one phrase.

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 values need not be explained, and the annotations carry the safety profile. The description covers the content scope adequately for a no-required-parameter catalog read; only the sibling differentiation and region/channel behavior are missing.

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%, so region and channel are fully documented in the schema and the baseline is 3. The description adds no meaning about them, and the phrase 'by ingredient key' could mislead an agent since no ingredient-key parameter exists.

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 names a specific resource (Chipotle's raw-ingredient content catalog) and enumerates its scope (sourcing story, imagery, menu items, recipe breakdown by ingredient key). It is far more specific than a tautology, but it is a noun phrase with no verb and never contrasts itself with siblings like chipotle_menu or chipotle_meals, so an agent must infer the differentiation.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. With seven sibling chipotle_* tools, the description does nothing to route the agent to this one versus chipotle_menu or chipotle_menu_metadata.

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