delivery_notes_convert

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

The description adds meaningful behavior beyond the annotations: it creates a new invoice with all delivery note data, marks the delivery note as converted, links the documents, and returns both. It does not warn about retry behavior or duplicate-risk implications of the non-idempotent annotation.

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 sentences deliver the core action, side effects, and return behavior without repetition. The conversion purpose is front-loaded and every sentence contributes.

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 mutation tool with no output schema, the description covers the main effects and returned documents, and the annotations communicate mutation and non-idempotency. It still omits operational preconditions such as whether the delivery note must be issued, unconverted, or otherwise valid before conversion.

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 all five parameters are already documented in the schema, including uuid, dueDate, issueDate, invoiceSeriesId, and companyId. The description does not add parameter-specific meaning beyond the schema, which is acceptable given full coverage but does not exceed the baseline.

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: 'Convert a delivery note into a final invoice.' It is clear what the tool does, but it does not explicitly distinguish this single conversion from the sibling tool delivery_notes_bulk_convert or other conversion-related tools.

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?

Usage is implied by the purpose statement: use it to turn a delivery note into an invoice. However, there is no explicit guidance about preconditions, alternatives such as bulk conversion or proforma conversion, or when not to use this tool.

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