Obtener información de comprobante

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, external read operation. The description adds that it retrieves 'información completa' of an already-issued voucher, but does not disclose authentication requirements, error behavior if the voucher is not found, or any rate limits.

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, front-loaded sentence with no wasted words. It efficiently communicates the core purpose without unnecessary elaboration.

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 read-only tool with three fully documented parameters and annotations covering safety, the description is minimally adequate. However, with no output schema, it should ideally hint at what 'información completa' includes (e.g., amounts, CAE, dates) or mention any authentication/authorization requirements for AFIP access.

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 all three parameters (PtoVta, CbteNro, CbteTipo) are already documented in the schema, including a reference to FEParamGetTiposCbte for CbteTipo. The description adds no additional parameter meaning beyond what the schema provides, so the baseline of 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 states a specific verb ('Obtener') and resource ('información completa de un comprobante'), clearly indicating retrieval of full voucher details. However, it does not distinguish this tool from siblings like get_last_voucher or mis_comprobantes, leaving ambiguity about when this specific retrieval is appropriate.

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 phrase 'ya emitido' implies the voucher must already exist, but there is no explicit guidance on when to use this tool versus alternatives such as get_last_voucher or mis_comprobantes. No exclusions or prerequisites are mentioned.

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