Importar Listas de Precio productos a SIIGO

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

The annotations already declare destructiveHint: true, so the agent knows this is a write operation. The description adds the valuable behavioral detail that the import result is left in the company's TEMP folder, which is beyond what annotations provide. It does not contradict the annotations.

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 with no redundancy. It front-loads the purpose and adds a single consequential detail about the output location, making it concise and well-structured.

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 the tool's complexity (8 parameters, destructive behavior, no output schema), the description covers the core purpose and output location but lacks information about success/failure behavior, prerequisites like authentication, or how to validate the import. The schema covers parameters, but the description does not fully contextualize the operation for the agent.

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 input schema has 100% coverage with detailed descriptions for all 8 parameters, including defaults, examples, and cross-references to other tools. The description itself adds no parameter-specific information, so the baseline of 3 is appropriate.

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 imports product price lists into SIIGO via the PUSHLIS function, specifying the resource (an .xlsx file) and destination (SIIGO). The explicit function name and target distinguish it from sibling tools like siigo_pushpre or siigo_pushlin, which likely handle different data types.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites such as requiring prior credential setup. The function name PUSHLIS is a hint, but the description does not differentiate it from other push tools or indicate when a different tool would be more appropriate.

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