sii_mipyme_list_dte_emitidos

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

No annotations are present, so the description carries the full transparency burden. It implies a read-only list operation and states the returned fields (folio, tipo, receptor, monto, estado), but it does not disclose requirements like an active session, rate limits, or potential errors beyond the basic operation.

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 sentence, front-loaded with the main action and resource. It efficiently conveys the system and output without unnecessary detail, earning every word.

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 no output schema, the description appropriately explains what is returned (folio, tipo, receptor, monto, estado). For a simple list tool with all optional parameters, this covers the essential context, though pagination and session prerequisites are not mentioned.

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 high (86%), so the schema already documents most parameters. The description adds no additional parameter-level meaning; it only lists the output fields, which does not increase parameter understanding beyond the schema.

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 lists the history of issued DTEs in the SII Free Invoicing System (mipyme.sii.cl), using a specific verb ('Lista') and resource ('historial de DTE emitidos'). It also names the system, distinguishing it from sibling tools that operate on other SII subsystems.

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 by explicitly naming the system (mipyme.sii.cl) and the scope (issued DTEs), which helps an agent decide when to use it. However, it does not mention alternatives or exclusion criteria, such as when to use sii_dte_list_documentos_emitidos instead.

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