add_to_cart

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

With no annotations present, the description carries the full burden, and it does well by stating that the order is not finalized, that confirmation is required later, and that there is a delivery lead-time constraint. It also conveys practical limits like quantity usually maxing at 2, which is useful behavioral context.

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 well structured with a purpose statement, caveats, an Args list, and a Returns note. It is slightly repetitive about calling confirm_order, but the organization is clean and information is front-loaded.

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 tool with no annotations and 5 parameters, the description is remarkably complete: it covers required parameters, defaults, valid formats, workflow follow-up, and delivery constraints. The presence of an output schema reduces the need to detail return values further, and 'Returns: Cart status' is sufficient.

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 0%, so the description is the only source of parameter meaning. It explains all five parameters: serve_date format, menu_line_id meaning with examples, profile optionality, quantity default/max, and menu_group_id default. This fully compensates for the empty schema descriptions.

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 has a specific verb ('Add') and resource ('meal to the shopping cart'), and explicitly says it does NOT place the order, which distinguishes it from confirm_order. This makes the tool's role immediately clear in the context of the sibling 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?

It clearly states that confirm_order must be called afterwards and that orders must be placed at least 1 day before delivery. It does not explicitly discuss alternatives like remove_meal or get_cart_status, but the workflow guidance is strong enough for an agent to know when to use this tool.

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