declaration_pdf

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

Annotations cover the safety profile (readOnly, non-destructive, idempotent, closed-world) and the description adds genuine operational context: which attachments are required per case (registration contract, amendment addendum, termination document or sworn statement), accepted formats, a 10 MB total cap, where the file lands when outFile is set, and that nothing is stored server-side.

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?

Front-loaded with the outcome ('Produce the PDF ANAF accepts'), then constraints, then next steps. The embedded parentheticals are dense but each carries decision-relevant detail (which document type satisfies which filing), so little could be cut without losing guidance.

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?

No output schema exists, yet the description explains both return modes (pdfBase64 in the response, or a written outFile) and the success handoff to submission. For a 5-parameter tool with two required inputs, nothing an agent needs to call it correctly is missing.

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 coverage is 80%, and the description still adds meaning by distinguishing the two attachment channels (local file paths in attachmentPaths vs base64 attachments) and by stating the aggregate size limit and permitted MIME types that the schema does not encode. It repeats that outFile causes a local write rather than adding new detail there.

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 concrete verb and artifact: renders the validated XML into the exact PDF form ANAF accepts, with the XML (and for C168 a zip of attachments) embedded. It is clearly distinguishable from declarations_download_pdf, invoices_pdf and receipt PDF tools because it names DUKIntegrator and ANAF's upload form as the target.

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?

Gives strong downstream context: with outFile the output is ready for agent_submit_declaration_pdf (qualified certificate) or manual SPV upload, and it names document_generate as the source of the sworn statement for a termination. It never explicitly contrasts itself with sibling PDF/declaration tools, so the when-not path is implicit rather than stated.

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