add_line_item

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

Beyond readOnlyHint=false, it discloses a write requiring ORDERS_W permission, explains that name/price are copied from catalog item, states no payment, and details the dry-run/confirmation behavior before writing. No contradiction with annotations.

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?

Front-loaded with a single-sentence purpose, followed by compact behavioral notes. Every sentence adds distinct info (copy semantics, dry_run/confirm, permission, payment exclusion). No 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?

For a 4-parameter write tool, the description covers permission, confirmation flow, side effects, and non-payment. With an output schema present and annotations provided, no critical context is 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 coverage is 0%, but the description adds meaning by identifying item_id as a catalog item and order_id as the target order, and by explaining dry_run and confirm. However, parameter names/IDs are not explicitly declared, so it's strong but not maximal.

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 states a specific verb+resource: 'Add a catalog item as a line item to an order' and clarifies the source (catalog item) and target (order). This distinguishes it from sibling tools like create_order and apply_order_discount.

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 clearly implies when to use it (adding a line item to an existing order) and provides workflow guidance: use dry_run to preview, confirm via elicitation or confirm=True. It does not explicitly contrast with alternatives or list when-not-to-use, so not a 5.

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