Identik Firma Electrónica

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

With no annotations this description carries the full burden, and it discloses the key traits: the returned URL is temporary (1 hour), requires no token, and the operation is gated on COMPLETED status. It omits whether repeated calls issue new URLs, error behavior for non-COMPLETED documents, and permission requirements.

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?

Two sentences, front-loaded with the return value and its expiry, followed by the clarifying contrast with the embedded certificate and the precondition. No filler; every clause carries information.

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 annotations and no output schema, the description adequately covers return values (temporary URL, expiry, contents) and the COMPLETED precondition. It leaves minor gaps around failure modes and permission requirements, but nothing an agent needs to invoke it correctly is missing.

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 coverage is 0% and the single parameter documento_id is never described in prose; the description only implies it must reference a COMPLETED document. For a trivial positive-integer ID a baseline 3 is reasonable, but the description adds no format or constraint detail beyond the schema's exclusiveMinimum.

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?

States a specific verb and resource ('Devuelve una URL temporal ... para bajar la constancia de firma como PDF') and enumerates exactly what the artifact contains (firmantes, fechas, IP, dispositivo, hash SHA-256). It explicitly distinguishes itself from the sibling descargar_documento_firmado by noting the constancia is already embedded in the signed PDF and this tool yields it as a separate file.

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?

Gives a clear precondition ('Sólo documentos COMPLETED') and an implicit when-to-use rationale (you want the certificate as a standalone file rather than inside the signed PDF). It does not name the alternative tool explicitly nor state what happens if the document isn't COMPLETED, so it stops short of full routing guidance.

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

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

With no annotations provided, the description carries the full behavioral burden and does useful work: it discloses that the return is a signed URL rather than the file bytes, notes the constancia is embedded, and specifies the 410 response after the retention period (plazo de resguardo). It omits permission/auth requirements and behavior for unsigned or missing documents.

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?

Two tight sentences with the core purpose front-loaded and the failure mode appended; no filler. Slightly terse relative to what the tool could document.

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?

No output schema or annotations exist, so the description must stand alone. It adequately covers the return type and one error case for a simple one-parameter tool, but lacks usage routing, identifier sourcing, and permission/edge-case behavior.

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?

Only one parameter, documento_id, and schema description coverage is 0%. The description never mentions the identifier or how/where to obtain it, so it fails to compensate for the missing schema documentation.

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?

States a specific action and resource: it returns a signed download URL for the signed PDF, with the constancia embedded at the end. This implicitly distinguishes it from siblings like descargar_constancia (proof only) and obtener_documento, though it never names an alternative explicitly.

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?

No when-to-use guidance, prerequisites, or routing to alternatives. It implies the document must exist and be signed, but leaves the agent to infer when this tool should be chosen over descargar_constancia or obtener_documento.

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

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

With no annotations, the description carries the full behavioral burden. It implies a read-only balance lookup but never states this, nor whether it requires authorization, whether it can fail for accounts without the optional modules, or how those conditional modules affect the response. Only the conditional content hint adds any value.

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 sentence that is front-loaded with the primary content ('Saldos de la cuenta'), but the trailing conditional clause about optional modules is vague and slightly obscures rather than sharpens the purpose.

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 no-parameter, no-annotation, no-output-schema tool, the description names the general content but does not describe the shape of the result or the conditions under which the optional sections appear. It is minimally adequate rather than complete.

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 has zero parameters, which is the baseline-4 case: there is nothing parameter-wise for the description to explain or compensate for.

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 says what the tool surfaces — account balances, document credits, and optionally biometric/WhatsApp/SMS verification status — so the resource is identifiable. But it has no verb, and the conditional 'si la plataforma los usa' muddies what will actually be returned. It does not differentiate itself from siblings like traza_auditoria or listar_documentos, though the resources differ obviously.

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?

There is no guidance on when to call this versus the sibling tools, no preconditions, and no mention of scope (own account vs. another). The agent must infer that this is a status/balance lookup available at any time.

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

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies a read-only listing and reveals possible status values, but does not state auth/permission needs, pagination behavior, or that no side effects occur.

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?

Single front-loaded sentence with no filler. Efficient and appropriately sized for the tool's low complexity.

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?

The purpose and status values are clear for this low-complexity list tool. However, with no output schema and no annotations, the description leaves return fields beyond status and pagination behavior unaddressed, creating minor 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?

Schema description coverage is 100%, so the optional 'pagina' parameter is fully documented in the schema. The description adds no parameter details beyond the status enumeration, which is output-related, so the baseline of 3 applies.

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?

Explicit verb 'Lista' and resource 'documentos del equipo', with enumerated status values. It distinguishes itself from siblings like listar_plantillas and obtener_documento by its plural team-document scope, though it does not explicitly name alternatives.

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?

No when-to-use guidance, prerequisites, or explicit alternatives are provided. Usage is only implied by the verb and resource combination.

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

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

With no annotations, the description carries the burden and does disclose what is returned (id and signers) and that templates originate in the web UI. It does not state that the call is read-only/non-mutating, nor how pagination behaves despite the 'pagina' parameter, leaving behavioral 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?

Two short sentences, front-loaded with the verb and resource, with the workflow note second. No filler, though the second sentence is arguably marginal given no sibling is named.

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 one-parameter list tool with no output schema or annotations, the description covers purpose and returned fields but omits pagination semantics and confirmation that it is a safe read. Adequate but with clear gaps for an agent planning pagination over results.

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?

There is a single optional parameter whose schema description coverage is 100% ('Página (por defecto 1)'), so the schema already documents it. The description adds no page-size, ordering, or filtering semantics beyond what the schema provides, making the baseline 3 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?

States a specific verb and resource ('Lista las plantillas del equipo') and names the return fields (id, firmantes), so the agent knows this is a read/list operation over team templates. It is distinguishable from crear_documento_desde_plantilla by scope, though it never names a sibling explicitly.

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 clause 'las plantillas se arman en la interfaz web; desde acá se usan para generar documentos' implies the workflow (discover template ids here, then generate documents), which suggests when to call it. However, it never explicitly names an alternative tool or states when NOT to use this one, so usage is inferred rather than directed.

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

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

With no annotations, the description carries the full burden, and it does disclose the returned payload shape (estado, meta, firmantes, envelopeId). However, it says nothing about permissions, behavior when the id does not exist, or side effects, so behavioral disclosure is partial.

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?

One front-loaded sentence that states the operation first, then enumerates return fields compactly. Dense but with no filler sentences; the only mild cost is the long parenthetical field list.

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?

Because there is no output schema and no annotations, the description's enumeration of return fields (estado, meta flags, signers with signingUrl/identity, campos, envelopeId) is valuable and largely fills the gap. It is still silent on failure modes and access requirements, so not fully complete.

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 single parameter has 100% schema description coverage ("El `id` numérico del documento"), so the baseline is 3. The description restates "`id` numérico" without adding format, range, or example details 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?

States a specific verb ("Devuelve") and resource ("un documento por su `id` numérico"), making it clearly the single-document fetch among siblings like `listar_documentos` or `descargar_documento_firmado`. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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 "por su `id` numérico" implies the lookup key, but there is no guidance on when to use this tool versus `listar_documentos`, `descargar_documento_firmado`, or `traza_auditoria`, and no exclusions or prerequisites are stated.

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

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

With no annotations, the description carries the full burden and does disclose the key non-obvious behavior: an all-or-nothing rejection that sends no emails, plus error-handling guidance (explain the reason, do not auto-retry). It stops short of 5 because auth requirements, idempotency, and rate limits are unstated.

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?

Three tight sentences, front-loaded with purpose and then the failure mode and follow-up guidance. Every sentence earns its place, though the imperative 'Explicá el motivo y no reintentes' is slightly advisory boilerplate.

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 two-parameter action tool with no output schema and no annotations, the description covers purpose, the atomic-failure behavior, and error handling. Missing only tangential details like auth scope and success confirmation, which is reasonable given there is no output schema to explain returns.

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 coverage is 50%: 'firmantes' is documented in the schema (recipientId from obtener_documento) and the description reinforces its semantics via 'firmantes pendientes' and signing order, but 'documento_id' is undocumented in both places and the description does not compensate. Baseline-to-marginal for partial coverage.

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?

States a specific verb and resource (reenvía el email a firmantes pendientes) with an added scope qualifier (respetando el orden de firma), which separates it conceptually from enviar_documento and obtener_documento. It does not name a sibling explicitly, so it falls just short of the top band.

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?

Gives clear context and an exclusion condition: the tool is for pending signers and the whole request is rejected if any chosen signer is still awaiting their turn. It does not name alternative tools for related needs, so it stops short of 5.

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

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

Sin anotaciones, la descripción asume toda la carga. Aporta que devuelve la traza en JSON, los campos incluidos y que resuelve el envelopeId automáticamente, pero no menciona permisos, manejo de errores, paginación ni otras características operativas relevantes.

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?

Dos oraciones breves y bien estructuradas, con la información principal al inicio. No hay relleno ni redundancia; cada frase aporta datos útiles sobre el propósito y el comportamiento.

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?

Para una herramienta de consulta con dos parámetros y sin esquema de salida ni anotaciones, la descripción cubre el propósito y el contenido de la respuesta, pero no detalla el parámetro pagina ni aspectos como permisos o estructura exacta del JSON devuelto.

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?

La cobertura de descripciones en el esquema es 0%, por lo que la descripción debe compensar. Explica que documento_id es un id numérico y que se resuelve automáticamente a envelopeId, pero omite por completo el parámetro pagina y su función de paginación.

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?

Especifíca claramente el verbo (Devuelve) y el recurso (traza de auditoría completa del documento), y detalla los eventos que incluye (creación, envío, apertura, firmas, con fecha/IP/dispositivo). No menciona ni diferencia explícitamente de herramientas hermanas como obtener_documento, por lo que no alcanza el nivel 5.

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?

No indica cuándo usar esta herramienta frente a alternativas, ni condiciones de uso, requisitos previos o exclusiones. La única orientación es implícita en la propia descripción del propósito.

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

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the operation is cryptographic verification and lists the specific checks performed plus that authentication is required ('equivalente autenticado'), but says nothing about the result format, cost, or permissions beyond the auth hint.

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?

Two tightly packed sentences: the action and its target come first, the enumerated checks follow, and the public-validator comparison closes it. Every clause earns its place with zero padding.

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?

There is no output schema, so the description bears some responsibility for indicating results, and it does so by enumerating the verification aspects (integrity, chain, timestamp, test status). It stops short of describing the shape of the verdict or error cases, which leaves a small gap for a validation tool whose output is the whole point.

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%: the single parameter pdf_base64 is fully documented with encoding and a 15 MB limit in the schema. The description adds only that the PDF may originate from Identik or an Argentine digital signature, which is context rather than parameter syntax, so the baseline 3 applies.

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?

States a specific verb ('Verifica criptográficamente') and resource ('las firmas de un PDF') and enumerates exactly what is checked: integridad, cadena, sello de tiempo RFC-3161, and test-document status. No sibling tool performs validation, so the agent can clearly distinguish it from the document-management siblings without opening a schema.

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 names an alternative ('el validador público /validar') and frames this as its authenticated equivalent, which hints at when to prefer it. However, there is no explicit when-to-use guidance within the workflow (e.g., after descargar_documento_firmado) and no when-not conditions against the sibling tools.

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