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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds nothing to reconcile the non-read-only hint for what is conceptually an extraction. It does not say how the case of a non-compliant PDF is handled, nor what the 'result file' actually is (raw .xml, a zip, a link), which is the key behavioral unknown here.

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?

Three short, front-loaded sentences with no padding. The last two sentences are thin, but they are not verbose.

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 output schema, the description must carry the return behavior, and 'Returns the result file' is too vague for an agent that needs to know whether it receives XML text, a base64 blob or a download reference. The failure mode for non-ZUGFeRD PDFs is also unaddressed.

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 100% and the nested file object documents name, upload_id, content_base64, the 50 MB cap and the 10-file limit. The description only restates format acceptance ('Accepts pdf'), so the baseline 3 applies.

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?

A specific verb+resource: pull the embedded invoice XML out of a ZUGFeRD/Factur-X PDF. It is clearly distinct from create-einvoice and einvoice-to-pdf by direction (extraction, not generation), though it never names those siblings explicitly.

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 when-to-use guidance: nothing tells the agent to prefer validate-einvoice first, or what happens with a PDF that lacks an embedded XML. The only implied condition is the file being ZUGFeRD/Factur-X, which is stated as fact rather than as a selection rule.

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