Documentos tributarios (facturas)

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral details like pagination and filtering options, but does not disclose additional traits such as authentication, rate limits, or default values. This is adequate given the strong annotation coverage.

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 concise sentences, front-loaded with the core purpose, and includes necessary details without any filler or redundancy. Every sentence contributes value.

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 simplicity (3 optional params, no output schema), the description covers the essential aspects: what is listed, key result fields, pagination, and available filters. Minor details like default page size or sort order are omitted, but the description is sufficiently complete for an agent to understand the tool's role.

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 (page, tipo, periodo) are fully described in the schema. The description merely reiterates the filter options without adding new semantic detail, matching the baseline for schema-heavy tools.

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 explicitly states 'Lista documentos tributarios emitidos y recibidos' (lists issued and received tax documents) with specific fields (folio, contraparte, montos). It clearly differentiates from sibling tools that target other resources like liquidaciones, trabajadores, or deudas.

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 provides clear context: it is used to list invoices (facturas), with pagination and filters by period and type. It does not explicitly mention alternatives or exclusions, but the resource scope is obvious from the name and description, making usage clear.

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