Listar enumeraciones de la API

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral detail beyond them: dual mode selection by presence/absence of 'nombre', and the delayed-failure trait of approximate names. It omits any note on caching or response size, but nothing contradicts the annotations.

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 sentences, zero waste, front-loaded with the resource and examples before the param behavior and the usage directive. Every sentence carries distinct 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 output schema, the description correctly supplies the return semantics (names without a parameter, values with one). For a single-optional-parameter read-only lookup, an agent has everything needed to call it correctly and interpret the result.

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 100% and the single optional parameter's description already documents the omit-to-list-names behavior. The description restates that semantics rather than adding format, casing, or case-sensitivity rules beyond the schema, 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 and resource (returns valid values of API enumerations) and enumerates concrete examples (tipoDocumento, tipoPago, unidadMedida, afectacionTributaria...). It also explains the two operating modes, so an agent can distinguish it from every sibling tool, none of which deals with enumeration lookup.

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 prescriptive when-to-use rule: 'Usala siempre antes de enviar un valor de enumeración', plus the consequence of skipping it ('un nombre aproximado falla recién al emitir'). No alternatives or when-not conditions are named, but no plausible alternative tool exists for this job.

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