Scarica PDF o XML di un documento

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds real context beyond them: the write target is the local FIC_DOWNLOAD_DIR folder, the return value is the file path, and it clarifies nothing is modified in Fatture in Cloud (reconciling the non-read-only hint with the fact that only local disk changes). It does not discuss overwrite behavior or file-size/rate constraints.

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 primary action and scope, then the routing hint. Slightly verbose because the same content is stated in both Italian and English, which duplicates rather than adds, but no sentence is filler.

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 download tool with no output schema, it covers everything needed: what gets fetched, the destination folder, the returned path, and the sibling alternative. Nothing required 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 description coverage is 0%, so the description must compensate, and it does for the `kind` enum by spelling out each value's meaning (issued document PDF, linked delivery-note PDF, attachment, e-invoice XML). document_id is only implicitly explained as the document to download, but it is self-evident from context.

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 (save to disk) and resource (PDF/DDT/attachment/e-invoice XML of an issued document), and explicitly distinguishes itself from fic_get_issued_document. An agent can identify the tool 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?

Gives an explicit when-to-use condition: 'Usalo quando serve il file e non basta il link temporaneo restituito da fic_get_issued_document', naming the sibling that returns the temporary link. Nothing is left to inference.

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