update_quote_line_item

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

With no annotations, the description carries full burden for behavioral disclosure. It only restates the action ('Update') without explaining whether it performs partial updates, what happens if the item does not exist, auth requirements, or return values. It adds no context beyond the name.

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 concise sentence with no fluff. It is front-loaded with the action and resource. Efficient for a simple update operation.

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?

Despite 6 parameters and no output schema or annotations, the description gives no operational context (e.g., whether it returns an updated object, error behavior, required permissions). It is not complete for a mutation tool; the schema covers parameters but not semantics.

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%, so parameters are documented in the schema. The description itself adds no parameter information, but per baseline for high schema coverage, the schema carries the meaning. No gaps in parameter definitions.

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 'Update a line item on a quote' clearly states the verb (update), resource (line item), and scope (on a quote). It distinguishes from siblings like add_quote_line_item, delete_quote_line_item, and update_quote by specifying the exact operation and target.

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. It does not mention fields that can be modified, prerequisites (e.g., quote existence), or cases where adding/deleting line items would be more appropriate. The description gives no exclusions or alternative references.

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