merit_create_sales_invoice

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

With no annotations, the description carries the behavioral burden and does it well: immutability, negative quantities for credit invoices, inline customer creation, and required payload semantics. It does not cover permissions or whether the endpoint triggers any sending side effect, so not 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?

Four dense sentences with no filler. The endpoint, core constraints, and required fields are front-loaded, and every sentence earns its 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?

The description never explains the internal structure of invoiceRows or taxAmount items, whose schemas are empty objects, so an agent cannot reliably construct them. There is also no output schema or response information, which is a significant gap for a 13-parameter mutation tool.

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?

Adds meaning beyond the schema: negative quantity/totalAmount for credit invoices, existing Id vs new-customer record shape, totalAmount as ex-VAT, and ISO date format. Schema coverage is only 62%, and nested taxAmount/invoiceRows items are untyped, so this added context is valuable, though several parameters remain undocumented.

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?

Opens with the specific action 'Create' and names the exact resource: 'Merit Aktiva sales invoice', also giving the endpoint POST /api/v2/sendinvoice. This clearly separates it from list/get/delete/email invoice 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?

Explicitly says invoices cannot be updated and prescribes delete-and-recreate, which is a strong when-not-to-use signal. It also gives credit-invoice guidance and required fields, though it does not name sibling alternatives like creating from a sales offer.

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