Importar Productos a SIIGO

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

Annotations indicate destructive behavior (destructiveHint=true), and the description does not contradict this. It adds useful context that the import result is placed in the company's TEMP folder, beyond what annotations provide. It does not detail permissions or error handling, but given annotation coverage, this is adequate.

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 exactly two sentences, front-loaded with the action and purpose. It contains no redundant information and is highly concise for an import tool.

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 an import tool with no output schema, the description explains the primary function and where results are stored (TEMP folder). However, it lacks details on expected file format, error behavior, or side effects beyond the destructive hint. Given the complete parameter schema and annotations, it is minimally viable but not fully comprehensive.

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?

All 8 parameters are fully described in the schema (100% coverage), so the description does not need to repeat them. The description adds no additional parameter-level detail beyond the schema, matching the baseline for complete schema coverage.

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 products to SIIGO from an .xlsx file, referencing the PUSHINV function. The verb 'Importar' and resource 'Productos a SIIGO' are specific, distinguishing it from sibling tools like pushmov or pushext.

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 clear context that this tool is for importing products to SIIGO from an Excel file, which implies when to use it. However, it does not explicitly name alternatives or state when not to use it, so it lacks full exclusion guidance.

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