enaho_descargar_documentacion

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

Annotations already provide safety hints (idempotent, non-destructive). The description adds that the tool returns ZIP paths for later reading with file tools, which is useful behavioral context, but it does not mention potential side effects, caching, or other operational details.

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 concise: two sentences. The first sentence states the action and objects, the second explains the output format and the dictionary's purpose. No unnecessary words or repetition.

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 that an output schema exists, the description does not need to list return fields. It provides sufficient context: what is downloaded, how the output is returned (ZIP paths), and why the dictionary is valuable. This is complete for a relatively simple documentation download tool.

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 description reinforces that the 'anio' parameter is the year ('del anio') and implies the dictionary is year-specific, but it adds no new semantic details about the 'encuesta' parameter beyond what the schema already provides. With 50% schema coverage, the description only marginally supplements the structured fields.

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 technical sheets, variable dictionaries, and questionnaires for a given year ('Baja ficha tecnica, diccionario de variables y cuestionarios del anio'). The verb 'Baja' indicates the action, and the specific resources distinguish it from data download or search tools among the siblings.

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 provides a concrete usage context by explaining that the dictionary resolves definition doubts that the catalog and index cannot. While it does not explicitly name alternative tools or exclusions, the purpose is clear enough to know when to use this tool versus others.

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