sii_dte_get_documento_recibido

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

No annotations are provided, so the description must bear the full burden. It discloses the digital certificate requirement and the conditional behavior for non-current-month documents, adding useful context. However, it does not describe the return format, error behavior, or what 'detalle' encompasses, leaving notable gaps.

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 short sentences, front-loaded with the core purpose and containing no filler. Every clause contributes value: purpose, a conditional parameter hint, and an important authentication requirement.

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?

For a specialized get-tool with no output schema and no annotations, the description covers purpose, authentication, and one parameter behavior. It does not explain return structure, pagination (if any), or edge cases like missing documents. Adequate for simple retrieval but with clear gaps.

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?

The schema already describes all 5 parameters with 100% coverage. The description adds meaningful semantics for fecha_doc by specifying when it is needed (if the document is not from the current month), which is not obvious from the schema alone. This elevates it above the baseline 3.

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 it retrieves details of a specific received DTE by folio, using the phrase 'Detalle de un DTE recibido específico por folio'. This distinguishes it from sibling tools like sii_dte_list_documentos_recibidos (list) and sii_dte_get_documento_emitido (emitted, not received).

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 this tool is for retrieving a specific DTE by folio, but it does not explicitly contrast with alternative tools or state when not to use it. It provides a conditional instruction for including fecha_doc for older documents, which is helpful but not a full alternative/exclusion guidance.

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