Importar Lineas y grupos de inventario a SIIGO

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

Annotations already indicate destructive hint (destructiveHint=true), and the description adds that the import result lands in the company's TEMP folder. This is useful context, but it does not disclose whether the import overwrites existing data, whether it is reversible, or any authorization requirements.

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 concise sentences. It front-loads the main purpose, includes a parenthetical reference to the SIIGO function name, and adds a relevant detail about the output location without unnecessary verbosity.

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?

The description covers the input format and output destination but does not explain return values or error handling beyond the logErrores parameter in the schema. Given the 8-parameter schema and no output schema, the description is adequate but leaves some operational context to be inferred.

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 tool description itself does not add any parameter-specific meaning beyond the schema; all parameter semantics are already captured in the input schema.

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 title and description clearly state that the tool imports inventory lines and groups ('Lineas y grupos de inventario') into SIIGO, and reference the specific SIIGO Pyme function PUSHLIN. This distinguishes it from the many sibling import tools, making the purpose unambiguous.

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 when to use the tool through its explicit mention of importing inventory lines/groups from an .xlsx file, but it does not explicitly state alternatives or exclusion criteria. Sibling tools like siigo_pushinv or siigo_pushlis are not referenced, leaving some inference needed.

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