parse_fattura_semplificata_xml

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

No annotations are provided, so the description carries the burden. It discloses the extraction scope, the success return shape, and the error return shape, which is more transparent than most parsers. It does not explicitly state 'read-only' or discuss side effects, but for a pure parsing function the description is sufficiently transparent.

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 efficiently organized: action, intended use cases, extraction summary, and return shape. It is front-loaded with the main purpose and every sentence contributes without unnecessary 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 there is an output schema and a single parameter already fully described, the description provides a complete picture: how to invoke it, what it extracts, and how it reports failures. It even references the related generator tool for a common use case.

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 input schema is concise and already documents the single parameter xml_string and its accepted VFSM10 format. The description adds no additional parameter-level semantics beyond what the schema states, so the baseline of 3 is appropriate.

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 clearly states it parses a FatturaSemplificata XML string into a structured Python dict, specifically for simplified invoices (TD07/TD08/TD09). It names the resource and action unambiguously and distinguishes itself from related invoice parsers by focusing on the 'Semplificata' subset and referencing the generator output.

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 explicitly states when to use it: to inspect simplified invoices received from counterparties or to verify output of generate_fattura_semplificata(). It provides clear use context, though it does not name alternative parse tools like parse_fattura_xml or explain 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.