Importar Catalogo de bodegas a SIIGO

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

Annotations declare the tool destructive and non-read-only, and the description does not contradict these. The description adds that the import result goes to the company's TEMP folder, providing some context beyond annotations. However, it does not disclose side effects on existing warehouse data or how success/errors are reported.

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?

Two sentences, front-loaded with the purpose, and includes the underlying function name and output destination. No redundant information or filler.

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?

With 8 parameters, no output schema, and a destructive annotation, the description gives the core purpose but leaves gaps: it doesn't mention the error log, the expected format of the .xlsx, or what the agent receives as a response. It is minimally adequate but not 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?

Schema description coverage is 100%, so all parameters are already documented. The description adds no parameter-specific details beyond mentioning the .xlsx input and TEMP output, which are not tied to individual parameters. 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 it imports a warehouse catalog to SIIGO from an .xlsx file and names the specific SIIGO function (PUSHTBO). It distinguishes the tool from sibling push tools by resource type (bodegas vs. other catalog 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 use case is implied by the purpose, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or conditions. The schema does reference siigo_list_companies for finding available companies, which is a minor usage hint for a parameter, but not for the tool overall.

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