sii_dte_get_documento_emitido

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

With no annotations, the description carries the burden. It discloses a key prerequisite ('Requiere certificado digital') and a conditional behavior (fecha_doc needed for non-current-month documents). However, it omits other behavioral aspects like response format, error conditions, or whether the operation is read-only.

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 concise and well-structured: two sentences that immediately state the main purpose, then add the conditional date hint and certificate requirement. No fluff or 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?

Given the tool's moderate complexity (4 params, no output schema), the description is reasonably complete. It covers the core purpose, the required certificate, and a key usage nuance. However, it could be improved by describing what the response contains or clarifying behavior when the document is not found.

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 schema already explains all parameters. The description adds a small amount of context for fecha_doc (when to use it), but this largely repeats the schema's explanation. No additional parameter meaning 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's purpose: 'Detalle de un DTE emitido específico por tipo y folio' (detail of a specific emitted DTE by type and folio). It uses a specific verb ('detalle') and resource, and distinguishes from sibling list tools and the received DTE getter.

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?

Provides clear context for when to use the tool: for a specific DTE by tipo and folio. It also gives a conditional usage hint for fecha_doc when the document is not from the current month, and notes the certificate requirement. However, it doesn't explicitly name alternatives or state when not to use it.

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