Leer un archivo xlsx

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

With readOnlyHint=true already in annotations, the description adds valuable behavioral context: the tool reads paginated, and it is restricted to SIIGO-generated files. It does not describe error handling or return format, but the annotation covers safety and the added pagination detail goes beyond the bare read-only hint.

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: the first states the core function (paginated reading of SIIGO xlsx files), the second gives the motivating use case. It is front-loaded and every word contributes, with no repetition of schema details.

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?

The description adequately covers the tool's purpose and the pagination scenario. There is no output schema, so a note about the return format would be helpful, but the description already provides enough context for an agent to select and invoke the tool correctly for the stated use case.

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 four parameters have schema descriptions, giving 100% coverage. The description reinforces the pagination concept (limit, offset) and the SIIGO-specific file source, but does not add significant per-parameter semantics beyond what the schema already provides. Baseline 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 uses 'Lee' (reads) with the resource 'cualquier .xlsx generado por SIIGO' and specifies paginated reading. It clearly distinguishes from sibling data-access tools like siigo_getmov or siigo_pushmov, which target specific entity types rather than file content.

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?

It states a specific use case: 'Util para recorrer un resultado grande despues de que una funcion de exportacion devolviera solo la primera pagina' (useful for traversing a large result after an export function returned only the first page). This gives clear when-to-use context but does not explicitly mention alternatives or when-not-to-use scenarios.

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