storno_xml_generate

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

With no annotations present, the description carries the behavioral disclosure burden and does so well: nothing is stored, no authentication needed, rate limited per IP, RON only, and the returned artifacts are explicitly listed (XML, XSD + Schematron validation report, totals). It omits details like rate-limit thresholds and failure modes, but the disclosed traits go well beyond the tool name.

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 description is compact but information-dense, front-loading the core purpose and then covering endpoint behavior, output, technical semantics, and use cases. Every sentence adds value; there is no filler or repetition.

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?

Given the tool's complexity, the description covers purpose, constraints, output contents, and usage scenarios. It also states key behavioral constraints (public, stateless, rate limited, RON only). It could be slightly more complete around error behavior and rate-limit specifics, but together with the detailed schema, an agent has enough to select and invoke the tool correctly.

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 useful semantic hints ('negated quantities', 'BillingReference to the original document', 'RON only') that map to lines, original, and currency. However, it does not enumerate or explain the required seller, buyer, original, and lines parameters, and top-level schema description coverage is 0%. The nested input schema is detailed, but the description itself only partially compensates for the missing top-level guidance.

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 names a specific verb and resource: generate an e-Factura (UBL 2.1, CIUS-RO) XML for a storno/credit invoice. It also distinguishes this tool from siblings like invoices_bulk_storno or delivery_notes_storno by emphasizing the public, account-less endpoint and the precise output type (Invoice 380 with negated quantities and BillingReference).

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 gives clear use cases: correct an invoice already accepted in SPV, or test XML output before integrating. It also conveys that this is the no-account/public-endpoint option. It does not explicitly state when not to use it or name alternative account-based tools, so it stops short of a 5.

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