declarations_download_pdf

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful context beyond that: generation happens from current data, Storno rules and ANAF validation run first, and errors are returned instead of a broken file. That failure-mode disclosure is exactly what an agent needs for a file-producing operation.

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?

Four dense sentences, front-loaded with what the file is, then when to use it, then where it lands, then validation behavior. Every sentence contributes, though the parenthetical file-format aside and portal navigation detail make it slightly heavier than strictly necessary.

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 correctly explains the return contract: a file written to outFile, or errors instead of a file when validation fails. Combined with the annotation safety profile, an agent has enough to invoke it correctly; only the sibling disambiguation is thin.

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 100%, so all four parameters are already documented. The description restates that output goes to outFile but adds no syntax, path conventions, or refresh semantics beyond what the schema provides. Baseline 3 applies when the schema carries the parameter burden.

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 precisely identifies the artifact: the ANAF-accepted PDF with embedded XML (plus attachment zip for C168), generated on demand. That is far more specific than the tool name alone. It does not explicitly contrast with close siblings like declarations_download_xml or declaration_pdf, leaving some ambiguity about which artifact-producing tool to pick.

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?

It gives a clear use case — the user files by hand and uploads the file in SPV or on the e-guvernare portal with their own certificate. That implicitly excludes the electronic-submission path (declarations_submit / agent), but no alternative tool is named explicitly.

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