sii_descargar_oficio

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds that this is a network fetch of a specific document, but it does not address the side effect implied by 'destino' (writing a file to disk) or note that only the size is reported when no path is given. Note the mild tension between 'Descarga...' writing to a path and readOnlyHint=true, though this is a conventional gray area for download tools.

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?

A single front-loaded sentence with zero waste: verb, resource, source domain and identifying keys in one pass.

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 simple download tool with full schema coverage and no output schema, the definition is nearly complete; only the file-write behavior of 'destino' and the fallback return (size only) are left to the schema, which is acceptable.

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 every parameter (anio, fecha, numero, destino) is already documented with format and defaults. The description only echoes that numero and fecha are the identifiers and adds no extra semantics, so the baseline 3 applies.

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 (descarga) and resource (PDF de un oficio de jurisprudencia administrativa del SII) and gives the identifying keys (número y fecha). This clearly separates it from search-oriented siblings like sii_buscar_resoluciones_y_oficios or sii_oficios_por_anio, though it does not name those siblings explicitly.

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 mention of 'identificándolo por su número y su fecha' weakly implies the caller must already know those values, but there is no explicit when-to-use/when-not or pointer to the sibling search tools to consult when the number is unknown. No prerequisites or alternatives are stated.

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