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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that a result file is returned, but says nothing about how the output is delivered (link, base64, temporary storage), whether it persists, or cost/limits beyond what the schema states. No contradiction with annotations.

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 short, front-loaded sentences with no filler: purpose first, then input/output summary. The phrase 'Accepts pdf, xml' is slightly telegraphic but does not waste space.

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?

For a nested-input conversion tool with no output schema, 'Returns the result file' is too thin — the agent cannot tell whether it receives a URL, a base64 blob, or a reference. Input side is adequately covered by the rich schema, but the return contract is left underspecified.

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%, so the meaning of files, name, upload_id, content_base64, and options.language is already fully documented in the schema. The description only reiterates accepted formats, adding no new parameter semantics. 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?

States a specific verb and resource (turn XRechnung XML / ZUGFeRD into a PDF) and names the exact input formats, which cleanly separates it from siblings such as validate-einvoice, extract-einvoice-xml, and create-einvoice. An agent can identify this as the rendering/conversion step without opening the schema.

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?

There is no statement of when to choose this over alternatives, no prerequisite (e.g. that the file must already be a valid e-invoice), and no exclusions. 'Accepts pdf, xml' is an input constraint, not usage guidance, leaving the routing decision to the agent.

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