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

With no annotations, the description discloses the output format and the important behavioral fact that every invoice has passed the KoSIT acceptance gate. It does not detail permissions, side effects, or rate limits, but covers the key behavioral promise.

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 a single, well-structured paragraph with the main function, output, verification guarantee, and keywords. It is concise with no filler, though a clearer separation of sections could improve readability.

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 (not shown), the description fails to explain the critical input parameters, leaving the agent uninformed about how to construct invoice_json and seller_profile. For a complex tool generating regulated documents, this is a significant gap.

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 description adds no meaning to the two opaque object parameters (invoice_json, seller_profile). The agent has no guidance on required fields, structure, or examples for these inputs.

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 it generates a KoSIT-verified ZUGFeRD/Factur-X German e-invoice, specifies output fields (pdf_b64, invoice_number, validation_report), and distinguishes from siblings like validate_einvoice by emphasizing the generation and verification aspect.

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 implies usage for generating a verified German e-invoice, but does not explicitly state when to use this tool versus siblings like validate_einvoice or compliance_status. No when-not or alternative guidance is provided.

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