wafeq_simplified_invoices_line_items_create

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

The description explicitly discloses that the operation is not idempotent, explains the consequence of calling twice, and gives actionable retry guidance with idempotency_key. This goes well beyond the annotations, which only state idempotentHint=false, by explaining why and how to mitigate it.

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 brief and front-loaded with the resource, endpoint, and write-status. There is minor redundancy between 'Create simplified invoice line item' and 'Endpoint for creating a new simplified invoice line item', but the overall structure is tight and every other sentence adds value.

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 description covers the core creation purpose, the non-idempotent behavior, and the retry-safety mechanism. The schema handles the body fields, and no output schema exists, so return-value details are not expected. It is slightly incomplete in not clarifying the distinction between simplified and regular invoices, but this is a minor gap.

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 schema already documents most body fields well, so the description's added value is its clear guidance on idempotency_key: pass it for safe retries or let the server generate one. This is meaningful parameter-level context beyond the raw schema. The invoice_id parameter is not described, but its role is obvious from the endpoint path and tool name.

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 states a specific verb and resource: 'Create simplified invoice line item' and includes the exact POST endpoint. It is unambiguous and distinguishes this tool from the many sibling line-item creation tools by naming the 'simplified invoice' 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 clearly implies this tool is for creating simplified invoice line items, but it does not explicitly state when to use it over alternatives such as wafeq_invoices_line_items_create. There are no exclusions or alternative tool references, so the usage guidance is present but implicit.

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