merit_create_invoice_from_sales_offer

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

With no annotations, the description carries the burden of explaining behavior. It clearly states this is a creation operation and cites the POST endpoint, which implies a mutation. It also specifies the return fields. However, it does not disclose side effects such as whether the original offer is marked as invoiced, whether conversion can be repeated, or any permission requirements.

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?

Two concise sentences convey the operation, endpoint, parameter meaning, and return value without any filler. Every sentence earns its place, and the most important information is front-loaded.

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 single-parameter conversion tool with no output schema, the description covers the input, operation, and return fields. It is nearly complete, though a note about the expected state of the offer or failure conditions would have made it 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?

Schema description coverage is 100%, so the schema already documents the required id parameter. The description adds minimal extra value by confirming 'id is the offer GUID', which is helpful for disambiguation but does not substantially go beyond the schema's 'Offer GUID (required)'.

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 action: 'Create a sales invoice from a Merit Aktiva sales offer', with the exact endpoint and input. This clearly differentiates it from sibling tools like merit_create_sales_invoice, which creates an invoice directly rather than converting an offer.

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 makes clear this tool is for converting an existing sales offer into an invoice, which is distinct from the many invoice- and offer-related siblings. It does not explicitly name alternatives or state when not to use it, but the offer-to-invoice transformation is unambiguous enough for an agent to select it correctly.

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