validate_fattura_semplificata_xsd

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

With no annotations provided, the description carries the full behavioral burden. It discloses that lxml is required, what gets validated (namespace, element structure, data types, cardinality), and all three return shapes: valid, invalid, and setup error. This exceeds typical coverage.

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 and well-organized: purpose first, then explicit call timing, then behavior, then return formats. Every sentence earns its place, with 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 that this is a single-parameter validation tool with no annotations, the description fully covers when to use it, what it requires, what it validates, and what the agent can expect in all outcome cases. Nothing needed to call it correctly is missing.

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?

Input schema description coverage is 100%, and the schema already explains the required root element and namespace. The tool description adds little parameter-specific detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific action ('validate'), a specific resource ('FatturaSemplificata XML string'), and a specific standard ('VFSM10 XSD v1.0.2'). It is immediately distinguishable from sibling validators such as validate_fattura_xsd, validate_ubl_invoice, and validate_cii_invoice.

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?

Explicitly instructs the agent to call this tool immediately after generate_fattura_semplificata() and to verify third-party simplified invoices. It does not explicitly name the alternative validate_fattura_xsd for non-simplified invoices, but the 'FatturaSemplificata' scope makes the boundary clear enough.

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