aruba_parse_invoice_xml

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

The description only states 'parse,' which aligns with readOnlyHint annotations, but adds no additional behavioral context such as decoding, validation, or redaction behavior. Does not mention what happens with invalid input.

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?

Extremely concise single sentence with no redundant information. Front-loaded with the main action.

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?

Despite having an output schema, the description lacks context about error handling, prerequisites (e.g., document must be valid FatturaPA), or how this parsing differs from other invoice tools. Insufficient for an agent to select correctly among many siblings.

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?

With 0% schema description coverage, the description must explain parameters, but it only implies xml_base64 is Base64-encoded. The redact_sensitive parameter is completely unexplained.

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 the tool parses Base64 FatturaPA XML into structured fields, specifying the verb and resource. However, it does not distinguish from siblings like aruba_extract_invoice_fields or aruba_validate_invoice_xml_structure.

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?

No guidance on when to use this tool versus alternatives such as aruba_extract_invoice_fields or aruba_validate_invoice_xml_structure. Lacks indications of prerequisites or exclusions.

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