It Parse Sdi Notification

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

With no annotations provided, the description must carry behavioral disclosure itself. It transparently states the input type and the output shape ('structured dict') and promises comprehensive coverage across all notification types. It does not disclose failure behavior on malformed XML or whether any normalization or validation occurs, but for a pure parse operation the core behavior is clear.

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 two sentences with no filler; the core action and output are front-loaded and the notification type codes are compactly listed in parentheses. Every sentence contributes selection-relevant 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?

Given a one-parameter tool with an output schema, the description provides the essential input context and full type coverage. It leaves error handling unspecified, but the presence of an output schema and the simple, read-only nature of parsing make the description adequate for selection and invocation. It could add a note about invalid XML handling, but nothing critical 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?

The sole parameter is 'notification_xml' and the schema gives no description (0% coverage), so the description must compensate. It does clarify that the expected payload is an SDI notification XML document, which is consistent with the parse behavior. But it does not explicitly state that the value should be the raw XML string as opposed to a path or reference, so the compensation is partial.

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 specific verb ('Parse'), the exact resource ('an SDI notification XML'), and the output ('a structured dict'). It also enumerates all supported notification type codes, which clearly distinguishes 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 first sentence establishes the use case: any time the agent has an SDI notification XML to convert. The list of notification type codes gives concrete selection criteria, and the word 'notification' implicitly separates this from the invoice-parsing siblings. However, it never names an alternative or states when not to use it, so it stops short of explicit exclusion guidance.

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