validate_invoice_pdf

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose real behavior beyond the name: the tool extracts embedded ZUGFeRD/Factur-X XML and validates against § 14 UStG, implying a read-only operation scoped to compliant e-invoice PDFs. It does not say what happens when no embedded XML is present, nor how results or failures are surfaced.

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?

Two compact clauses: the purpose ('Direkte Prüfung einer PDF-Rechnung in einem Schritt') is front-loaded, followed by the mechanism. Every phrase carries information, though the framing colon structure is slightly less scannable than a single sentence.

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?

With no annotations and no output schema, the description must cover the full picture. It explains what is extracted and which standard is applied, but omits return shape (pass/fail, error list) and edge cases such as PDFs without embedded XML, leaving meaningful gaps for a validation tool.

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 description coverage is 0% and the single parameter 'invoice_pdf_name' is undocumented in the schema. The description partially compensates by establishing that the input must be a PDF invoice carrying embedded ZUGFeRD/Factur-X XML, which narrows the expected file type, but it gives no format, path, or naming guidance.

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 (Prüfung/validiert) and resource (PDF-Rechnung), and clarifies the mechanism: extracting embedded ZUGFeRD/Factur-X XML and checking conformity with § 14 UStG. The phrase 'in einem Schritt' implicitly distinguishes it from the parse/validate sibling pair, but it stops short of naming them.

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?

'In einem Schritt' (in one step) hints that this is the combined alternative to calling parse_invoice and validate_compliance separately, but no sibling is named and no when-not condition is given. Usage is implied rather than explicit, so an agent must infer the routing decision.

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