sii_descargar_oficio

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says it downloads the PDF; it does not mention that the file is saved to 'destino', what happens when 'destino' is omitted, possible errors, or whether the operation is safe/read-only.

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 a single concise sentence that front-loads the action and resource. It is not bloated, though it is slightly too terse given the absence of annotations and output schema.

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 and no annotations, the description should explain what the tool returns or where the PDF is saved, especially because 'destino' is optional. It also lacks any connection to related SII search tools, leaving an agent without enough context to invoke it correctly in a broader workflow.

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 100%, so the baseline is 3. The description merely repeats the concepts of número and fecha de publicación already present in the schema and adds no meaningful detail about anio or destino.

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 uses a specific verb ('Descarga') with a clear resource ('el PDF de un oficio de la jurisprudencia administrativa del SII') and identifies the two key selection criteria: número and fecha de publicación. This distinguishes it from sibling search/list tools like sii_buscar_resoluciones_y_oficios and sii_oficios_por_anio.

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 gives no explicit guidance on when to use this tool versus related alternatives. It does not state that the user should already know the número and fecha, nor that search tools should be used first when those identifiers are unknown.

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