wafeq_simplified_invoices_line_items_update

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

The annotations already declare this as a non-readonly, non-destructive, idempotent write operation, and the description's WRITE marker is consistent with that. The description adds no meaningful behavioral context beyond the annotations, such as what fields get overwritten, side effects on totals, or authorization requirements.

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 first line is dense and front-loaded with the route and operation category, but the following two sentences both restate the same idea: 'Update simplified invoice line item' and 'Endpoint for updating an existing simplified invoice line item.' This redundancy makes the definition less concise than it should be.

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 nested-body update operation with no output schema and a partial-update sibling, the definition should explain full replacement semantics, whether omitted body fields are reset, and what response the caller can expect. The description only restates the endpoint and leaves critical context for the agent to infer.

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?

The route template usefully reveals that invoice_id and id are path parameters, but the description does not clarify how the body should be structured for a full update. The schema's nested body properties are reasonably self-documenting, yet the generic ModelSerializer text does not compensate for the 50% schema description coverage.

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 clearly states the verb ('Update') and resource ('simplified invoice line item'), so an agent can tell what operation is being exposed. However, it does not contrast itself with the sibling 'wafeq_simplified_invoices_line_items_partial_update', leaving the full-vs-partial update distinction implicit.

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?

There is no guidance on when to use this tool instead of the partial-update sibling, nor any explanation of PUT semantics vs PATCH. The only hint is the HTTP method in the route, which is not expanded into actionable usage direction.

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