it__parse_sdi_notification

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

With no annotations provided, the description carries the full burden. It discloses that the operation is a parse into a structured dict and enumerates supported notification types, but it does not describe behavior for malformed XML, unknown notification types, or validation failures. This is adequate but not deeply 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 intentionally succinct: two sentences. The supported-type list is compact yet valuable, and every sentence adds real selection and invocation information.

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 one-parameter parser with an output schema available, the description covers the input domain thoroughly by listing all notification types. The only notable omission is failure-mode behavior, which is not critical enough to make the description incomplete for normal usage.

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 coverage for the single parameter is 0%, but the parameter name notification_xml combined with the description's first sentence makes the intended input unambiguous. No complex formats, defaults, or enums require additional explanation.

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 is specific: it names the verb 'Parse', the resource 'SDI notification XML', the output 'structured dict', and enumerates exactly which notification types are supported. This clearly differentiates it from sibling invoice-parsing tools such as parse_fattura_xml or parse_ubl_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?

The description establishes clear context for when to use the tool: any SDI notification XML matching the listed types. It does not explicitly name alternatives or say when not to use it, but the supported-type list makes the usage boundary reasonably obvious.

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