Extraer Formulacion Presupuesto de venta

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by disclosing that the tool generates an .xlsx file and returns the first parsed rows, which is relevant behavioral context beyond the annotations. It does not mention potential file overwriting, but the annotation safety profile mitigates the need.

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 a single, front-loaded sentence that states the resource, function, and output behavior. Every word earns its place with no redundancy.

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 11 parameters and no output schema, the description gives a concise but adequate overview: it names the SIIGO function, states the file output, and explains the parsed row preview. The schema descriptions cover parameter semantics, and the annotations cover the safety profile, so the description is reasonably complete for the tool's complexity.

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 description itself does not add parameter-specific meaning beyond what the schema already provides, but it does mention file generation and preview, which indirectly relates to filasPreview and archivoSalida.

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 uses a specific verb ('Extraer') and resource ('Formulacion Presupuesto de venta'), names the underlying SIIGO function (GETPRE), and clarifies the output behavior (generates .xlsx, returns parsed rows). This clearly distinguishes it from siblings like siigo_getmov or siigo_pushpre.

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 for when to use this tool: extracting sales budget formulation data from SIIGO. It does not explicitly mention alternatives or exclusions (e.g., siigo_read_xlsx for existing files), but the function name and behavior imply the intended use case.

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