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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description owes context on the risk: it does not say whether items are appended to or replace existing line items, whether retries duplicate rows, or whether change order totals/markups are recalculated. 'Adds' is the only behavioral signal, and it does not resolve the append-vs-replace question critical for a destructive call.

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?

One short, front-loaded sentence with no filler. It is efficient, though it is efficient partly because so little is said.

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 destructive, non-idempotent write with no output schema, the definition omits the essentials: append vs overwrite semantics, duplicate-on-retry behavior, permissions, and what is returned (created item ids or the updated change order). An agent cannot call this safely and predictably from the current text alone.

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 50% and the nested item properties (name, unit, unit_cost, cost_code_id, description) are already documented inline, so the schema carries most of the load. The description adds only the word 'priced', hinting that unit_cost is required, and says nothing about batching limits (maxItems 100) or the change_order_id source.

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?

Specific verb (Adds) plus resource (priced line items) and target (change order / change order request), which separates it from siblings like add_estimate_items and add_invoice_items. The ambiguity between 'change order' and 'change order request' is never reconciled with the single change_order_id parameter.

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 statement of when to use this versus add_estimate_items/add_invoice_items, nor prerequisites such as needing an existing change order id. The reader must infer that a change order must already exist and that this is the follow-up to create_change_order.

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