wafeq_invoices_line_items_partial_update

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

Annotations already declare this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the HTTP method and update semantics, but says nothing about side effects, response behavior, or which fields are affected. No contradiction with annotations exists.

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 short and front-loaded with the method and resource, which is good. However, 'Partial update invoice line item' and 'Endpoint for partially updating an existing invoice line item' redundantly restate the same fact, so structure is functional but not tight.

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?

Given the complex nested body, lack of output schema, and many sibling line-item tools, this description is too thin. It does not define what 'partial' means operationally, which fields can be updated, how the idempotency key works, or how this tool differs from wafeq_invoices_line_items_update.

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 description does not explain any parameters. The body parameter's schema description is unrelated to the line item body itself, mentioning custom_fields and CALCULATED fields, which is confusing. The schema provides descriptions for many nested fields, but the top-level body, id, and invoice_id parameters are poorly documented and the description does not compensate.

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 and resource: 'Partial update invoice line item' with endpoint PATCH /invoices/{invoice_id}/line-items/{id}/. It is distinguishable from sibling tools like wafeq_invoices_line_items_update by the explicit 'partial' qualifier, though it does not explicitly name that sibling.

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 gives no guidance on when to use this tool versus the full-update sibling or when a partial update is appropriate. It does not state prerequisites such as the invoice or line item needing to exist, nor does it exclude cases where full update is required.

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