chipotle_add_to_bag

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the action without detailing side effects (e.g., whether it appends or replaces items, requires an existing bag), error conditions, or confirmation of success. For a mutation tool, more transparency is expected.

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 extremely concise with only two sentences. The first sentence directly states the purpose, and the second provides essential sequential guidance. Every word earns its place with no filler or redundancy.

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 tool's simplicity (one optional parameter, no output schema, no annotations), the description covers the basic action and sequence but lacks details on default behaviors (e.g., quantity defaults to 1), return values, or error states. It is minimally complete but not fully informative for an agent.

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?

The input schema has 100% coverage with a description for the quantity parameter. The tool description does not add any extra meaning beyond the schema; therefore, it meets the baseline score of 3. No additional parameter context is needed.

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 verb ('Add') and resource ('the currently configured item to your bag'), and the sibling tools confirm distinct purposes like viewing bag or checkout. The mention of calling after chipotle_start_order and chipotle_customize_item adds clarity on the workflow context, though it could be more explicit about the scope of 'currently configured item'.

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 explicitly states the sequential dependency: 'Call after chipotle_start_order and chipotle_customize_item.' This provides clear context for when to use the tool. However, it does not mention when not to use it or list alternative tools like chipotle_view_bag for checking bag contents, but the context is sufficient for an agent.

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