chipotle_customize_item

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'customize,' implying mutation, but does not describe whether multiple calls override or append, validation rules, or error conditions. This lack of detail makes it insufficient for an agent to understand side effects.

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 sentence plus a clear ordering instruction, with zero wasted words. It is front-loaded and easy to parse.

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 the complexity (5 parameters, no output schema), the description covers the high-level purpose but omits important details like the return value, whether customization resets after adding to bag, or any constraints on combinations (e.g., can't have both rice and beans). It is adequate but has clear gaps.

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% with detailed parameter descriptions (enums, examples). The description adds no additional meaning beyond listing categories (protein, rice, etc.), so it meets the baseline but does not improve understanding of parameter interactions or constraints.

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 customizes an order item by adding specific components (protein, rice, etc.) and explicitly mentions it should be called after chipotle_start_order, distinguishing it from sibling tools like chipotle_start_order and chipotle_add_to_bag.

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 provides explicit usage context by stating 'Call after chipotle_start_order,' which tells the agent when to invoke the tool. However, it doesn't mention when not to use it or any alternatives, but the instruction is clear enough for a single customization step.

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