Add embedded file attachment (PDF/A-3, Factur-X)

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

Discloses PDF/A-3b conformance, 8 MiB attachment cap, auto-emission of minimal cover, and that PDF/A-3 is the only PDF/A part permitting embedded files. No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).

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?

Concise and well-structured: front-loads purpose, uses imperative tone, and every sentence adds value without redundancy.

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?

Covers core functionality, usage context, constraints, and parameter behavior. Output schema exists so return values need not be explained. Slight lack of detail on outputMode/outputPath behavior, but schema provides enum and structure.

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?

Adds contextual meaning beyond schema: explains Factur-X attachment requirements (relationship=Source, mimeType=application/xml), block schema reuse, and size cap. The outputPath parameter lacks description in schema but tool description doesn't add to it; however, schema coverage is high enough.

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?

Clearly states it generates a PDF/A-3 document with embedded files, specifies Factur-X/ZUGFeRD use case, and explicitly distinguishes from sibling generate_basic_pdf.

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?

Explicitly says 'USE THIS INSTEAD OF generate_basic_pdf when you need a Factur-X / ZUGFeRD electronic invoice', provides context for when to use the tool, and notes that blocks parameter is optional.

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