wafeq_credit_notes_line_items_create

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

The description explicitly warns 'Not idempotent — calling twice creates two records' and explains that passing idempotency_key makes retries safe, going beyond the idempotentHint=false annotation. It does not mention other side effects such as validation failures or response shape, so it stops short of a 5.

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 dense and front-loaded with the WRITE indicator, resource, and endpoint, but the description then repeats the same fact three times: 'Create credit note line item', 'Endpoint for creating a new credit note line item', and the opening line. The redundancy wastes tokens and makes the structure less crisp than it could be.

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 essential mutation behavior and idempotency concern, and the schema handles required fields. However, with no output schema, the description does not mention what the endpoint returns, and it does not note prerequisites such as the credit note existing, making it adequate but not fully self-contained.

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 tool description adds little parameter-level meaning beyond the schema; the idempotency_key advice essentially repeats the schema description. Schema coverage is 67% and the nested body fields are individually documented, so the agent can infer required inputs, but the body parameter's own schema description is confusingly about output augmentation and the tool description does not correct it.

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 opens with a clear WRITE label, names the exact resource 'Credit Note Line Items', and gives the POST endpoint '/credit-notes/{credit_note_id}/line-items/'. It unambiguously identifies this as the creation tool among the many line-item siblings.

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 states that this endpoint 'creates a new credit note line item', so an agent can clearly select it when adding a line item to a credit note. It does not explicitly contrast it with update/destroy/list alternatives, so guidance is clear but not fully exclusive.

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