wafeq_simplified_invoices_update

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description adds the explicit PUT endpoint, which hints at full-replacement semantics. It does not, however, disclose that a PUT overwrites the existing invoice and requires all required body fields to be re-supplied — a key behavioral trait of this operation that the description leaves to inference.

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 WRITE badge and endpoint path. The three clauses 'updates data', 'Update simplified invoice', and 'Endpoint for updating an existing simplified invoice' are near-duplicates, wasting a sentence's worth of space on repetition.

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 tool with a deeply nested body schema and no output schema, this description is a minimal stub that explains neither the PUT replacement semantics nor what the response looks like. The idempotency_key guidance lives only inside the schema, so crucial invocation details are left for the agent to discover on its own.

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 67%, with useful per-field descriptions on most body properties (status, currency, place_of_supply, line_items) and a thorough explanation of idempotency_key. The description text itself adds zero parameter meaning, but at this coverage level the schema carries the weight, so baseline 3 applies; the unhelpful 'Adds nested create feature' body description is a minor detractor.

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 the verb (update), resource (simplified invoice), and HTTP method (PUT /simplified-invoices/{id}/), so an agent can tell what this tool acts on. However, it does not explicitly contrast itself with the sibling wafeq_simplified_invoices_partial_update, leaving differentiation to be inferred from the PUT method rather than stated intent.

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 conditions, prerequisites, or exclusions are stated in the description. With siblings like wafeq_simplified_invoices_partial_update, wafeq_simplified_invoices_create, and wafeq_invoices_update, an agent gets no cue about when to choose this tool over those, which is a meaningful gap.

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