wafeq_debit_notes_line_items_create

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

The description clearly discloses non-idempotency ('Not idempotent — calling twice creates two records') and explains how idempotency_key makes retries safe, adding useful context beyond the idempotentHint=false annotation. It also leads with 'WRITE · creates data', consistent with readOnlyHint=false.

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 front-loaded banner and idempotency warning are useful, but 'Create debit note line item' and 'Endpoint for creating a new debit note line item' repeat the same information. Several segments are redundant rather than earning their place.

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 create call, the description gives the route and retry semantics but no description of the expected response or any guidance on the body contract; the schema must carry that weight. With no output schema and a poorly described body parameter, some context is missing, though the annotations cover the safety profile.

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 adds no new detail about the body fields or debit_note_id; the path template is the only parameter hint it provides. The schema already documents most fields, but the required body shape is left entirely to the schema, whose body description is an unrelated output note.

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 ('Create') and resource ('debit note line item'), and provides an exact POST path with debit_note_id. It is clearly distinguishable from sibling tools targeting line items on other document types.

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 implies its usage by labeling itself as the endpoint for creating a new debit note line item and warns against duplicate calls. However, it does not mention alternatives such as update, partial_update, or destroy, nor does it state explicit when-not-to-use conditions.

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