storno_xml_generate

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

Beyond the annotations, it discloses that nothing is stored, no authentication is needed, rate limiting is per IP, and it returns XML plus XSD/Schematron validation report and totals. It also explains the output structure as type 380 with negated quantities and BillingReference, which is substantial behavioral context for a tool with no output schema.

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 front-loaded with the core purpose and then packs auth, storage, output, format, business meaning, currency, and usage into a compact block. There is no significant filler, though 'exactly what Storno issues for stornos' is slightly redundant but still clarifying.

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 complex nested generator with no output schema, the description covers what it returns, that it validates against XSD and Schematron, what business document it produces, its currency limitation, and the expected use cases. Remaining field-level detail is appropriately delegated to the input schema.

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 some meaning: currency is RON only, the storno references an original document, and output quantities are negated. However, it does not compensate for low schema coverage by explaining seller, buyer, line-item, or required-field semantics; the nested schema must carry most parameter documentation.

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 precise verb and resource: generate an e-Factura UBL 2.1 CIUS-RO XML for a storno / credit invoice. It clearly distinguishes this from normal invoice tools by noting it works without an account and produces an Invoice type 380 with negated quantities and a BillingReference to the original.

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?

It gives explicit use cases: correct an invoice already accepted in SPV, or test XML output before integrating. It also clarifies the public no-auth context. It does not name sibling alternatives or explicit when-not conditions, so it falls short of the top usage-guidance level.

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