Listando tipos de selección

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

With no annotations, the description carries the full burden. It discloses the return shape ({'ok','tipos':[{codSeleccion, descSeleccion}]}), which is useful, but says nothing about read-only nature, caching, or any other behavioral trait. Adequate but thin for an unannotated tool.

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?

Structured with clear Args and Devuelve sections, front-loaded with the tool's identity. Every line is relevant; only the mixed Spanish/English drift adds minor noise.

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 catalog tool with no output schema and no annotations, the description supplies both the input meaning and the return structure, plus the link to buscar_contratos. Reasonably complete for its complexity.

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 0%, so the description must compensate. It explains the single parameter 'anio' as the year of the catalog with an example ('2026'), adding real meaning beyond the bare string schema and its default.

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 resource: the exact catalog of selection types from the contracts JSON API ('Catalogo EXACTO de tipos de seleccion'). It's clear what the tool returns, though it doesn't explicitly contrast itself with sibling catalog tools like listar_filtros or catalogo_ubigeo.

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?

Usage is implied rather than stated: by noting that 'codSeleccion' is the value of 'cod_seleccion' in buscar_contratos, it hints the catalog is meant to feed valid codes into that sibling. There is no explicit 'when to use this vs alternatives' or exclusion guidance.

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