Importar Activos a SIIGO

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

Annotations already declare destructiveHint=true, and the description adds that results are placed in the TEMP folder of the company, which is useful contextual detail. However, it does not elaborate on side effects or irreversible changes beyond what annotations convey, leaving some gaps.

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, front-loaded with the action ('Importar Activos a SIIGO' and 'Importa a SIIGO'). It contains no fluff, though it could be slightly longer to include more behavioral guidance without losing clarity.

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 destructive import operation with 8 parameters and no output schema, the description is thin. It lacks information about expected input file structure, error handling, or the effect on existing data. The only useful detail is the TEMP folder output, leaving many important aspects unexplained.

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 have detailed descriptions in the input schema, including defaults and examples, so the schema covers parameter semantics fully. The tool description adds no additional parameter information, which is acceptable given the high 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 assets to SIIGO from an .xlsx file, with a specific verb and resource. It mentions the SIIGO PUSHACT function, which helps distinguish it from other siigo_push* tools, though it could be more explicit about being the right choice for asset imports only.

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?

There is no guidance on when to use this tool versus alternatives like siigo_pushmov or siigo_pushext. It does not mention prerequisites, file format requirements, or that this should be used specifically for asset imports.

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