wafeq_simplified_invoices_line_items_partial_update

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

Annotations already cover readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds only a generic 'WRITE / updates data' label and the PATCH method, without disclosing side effects, required permissions, or the nuance that only provided fields are changed. No contradiction with annotations.

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 a good front-loaded summary, but the second and third lines repeat the same 'partial update' concept. Compact, yet slightly redundant.

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?

The schema and annotations carry much of the context (field descriptions, idempotency, non-destructive write). Still, the description omits partial-update semantics (only supplied fields change), return-value expectations, and any guidance on valid field combinations, which matters for a nested-object PATCH endpoint.

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 path template adds useful context that invoice_id and id are URL parameters, and the schema already describes the body fields and idempotency_key. However, the description does not explain how the body maps to a partial update, and coverage is only about 50%, so the description itself contributes limited parameter meaning.

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 names an exact verb ('partial update'), a specific resource ('simplified invoice line item'), and the HTTP method/path. 'Partial update' clearly separates it from the full-update and destroy siblings for the same resource.

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 only restates that this endpoint partially updates an existing line item. It gives no explicit when-to-use guidance, no alternative recommendation (e.g., full update vs partial update), and no prerequisite such as requiring the invoice and line item to exist.

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