sii_dte_list_documentos_emitidos

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

No annotations are provided, so the description must carry the full behavioral burden. It only discloses the digital certificate requirement. It does not mention that this is a read-only operation, whether a session is needed, any rate limits, or what kind of response to expect. Minimal behavioral detail.

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?

A single, concise sentence that front-loads the verb and resource, and includes the key prerequisite. No fluff or repetition; every word earns its place.

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 6 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, pagination behavior, or error conditions. For a listing tool with moderate complexity, more context is needed for an agent to know what to expect.

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 (83%), so the schema already documents most parameters. The tool description adds no extra semantic details beyond the schema, but the parameter names are mostly self-explanatory. 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 a specific verb ('Lista') and resource ('DTEs emitidos por la empresa') within the SII DTE consultation context. This clearly distinguishes it from sibling tools like 'sii_dte_list_documentos_recibidos' or 'sii_dte_get_documento_emitido'.

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 implies usage when needing to list issued DTEs, and it mentions a prerequisite (requires digital certificate). However, it offers no explicit comparison to alternatives like 'sii_mipyme_list_dte_emitidos' or 'sii_dte_list_documentos_recibidos', so usage context is mostly implied.

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