add_line_items_to_order

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

With no annotations, the description carries the full burden, but it only states the action without disclosing behavioral details. It does not explain whether line items are appended, whether existing line items are affected, how pricing or quantities are handled, or any 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 clear sentence of six words, which is appropriately concise and front-loaded. It avoids verbosity, though it is minimal to the point of bordering on under-specification.

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 no output schema and no annotations, the description is incomplete. It leaves unclear how the operation behaves (e.g., whether it recalculates totals), what the success/error responses look like, and any constraints on order state. The minimal schema descriptions do not compensate for these 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 description coverage is 100% for all properties (e.g., 'Quantity', 'Custom price (optional)'), so the baseline is 3. The description itself adds no additional meaning beyond what the schema already provides, but it does not detract either.

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 uses a specific verb 'Add' with direct object 'line items' and target 'to an order', clearly stating the action. It distinguishes itself from the sibling tool 'remove_line_items_from_order' by indicating the opposite operation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as the order being open, nor any comparison with other order-editing tools like 'update_order' or 'remove_line_items_from_order'.

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