download_heu_document_pdf

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

With no annotations provided, the description carries full behavioral burden. It states the tool saves locally and returns path but does not disclose important traits such as overwrite behavior, error handling, authentication needs, or network requirements. The minimal disclosure is insufficient for a mutation-like 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?

The description is two sentences, efficiently conveying the core function and one key optional parameter. It is front-loaded with the main action and result. However, it could be more structured (e.g., listing optional parameters) but remains concise without waste.

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?

Given 5 parameters, no output schema, and no annotations, the description covers the main function and layout parameter but omits detailed behavior for optional parameters like has_index, has_footer, and output_path. It is adequate for the core purpose but leaves gaps for comprehensive use.

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?

The schema covers all 5 parameters with descriptions. The description adds value by explaining the layout parameter as codes from the HEU UI ('codici a 3 cifre della UI HEU'), which is not evident from the enum list alone. Other parameters are not elaborated, but schema coverage is high, so baseline is 3, and the layout insight raises it.

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 clearly states the tool downloads a PDF of an HEU document, saves it locally, and returns the file path. It specifies the object (HEU document) and action (download and save PDF), distinguishing it from siblings like get_heu_document or read_heu_document which likely return content directly.

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?

The description implies usage for downloading PDFs but provides no explicit guidance on when to use this tool versus alternatives. It mentions the optional layout parameter from the HEU UI but does not give prerequisites or scenarios where other tools are preferred.

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