Add change order items

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

Annotations already declare that this is not read-only, is open-world, and is not idempotent. The description adds useful behavioral context: items are appended to the first section, the app computes totals, and the result includes saved items plus the new total. It does not discuss permissions or error behavior, but the annotations carry the safety profile.

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?

Three tightly written sentences with no filler. The core action and scope are front-loaded, followed by item details and return behavior.

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 mutation tool with annotations and no output schema, the description covers what is added, where it is added, that totals are computed, and what is returned. Minor omissions like item limits or error conditions are handled by the schema or are not essential for correct invocation.

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 50%, so the description should compensate more than it does. It names most item fields and the allowed type values, which is helpful, but it omits the cost_code_id and description fields and does not clarify top-level parameters beyond their 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?

States a specific verb and resource: adds priced line items to a change order or change order request. It is clearly distinguishable from generic change-order tools, but it does not explicitly contrast with sibling item-adding tools such as add_estimate_items or add_invoice_items.

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 usage context is implied by 'adds line items at the end of the change order's first section,' but there is no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer this is for adding items to an existing change order, but the description does not route it against siblings.

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