buscar_pac

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

With no annotations, the description carries the full burden and does well: it explains that entidad is required because the site forces choosing institution or ubigeo, and that the year catalog only spans 2019..2026. It omits auth/permission needs and any pagination behavior, which keeps it short of a 5.

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?

Front-loads the purpose, then structured Args and Devuelve blocks. Slightly verbose in the row-field enumeration, but each section earns its place and there is no filler.

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 and no annotations exist, yet the description documents the return envelope (ok, entidad, anio, total, filas with item/entidad/ubigeo/ultima_version/cantidad_procesos/valor_proceso_soles) and the drill-down path. An agent has everything needed to call and interpret it.

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%, so the description must compensate and it does: it defines entidad (name or partial name, example 'SEDAPAL', required and why), and anio (example '2026' with the valid range 2019..2026). This adds real meaning beyond the bare schema types.

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 (Busca) and resource (PLANES ANUALES DE CONTRATACIONES / PAC) scoped to SEACE, plus the two filters (entidad, anio). It also names the sibling detalle_pac for the follow-up drill-down, so an agent can distinguish it from buscar_procesos and the other buscar_* tools.

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 (public PAC lookup by entity+year) and explicitly routes the agent to detalle_pac(...) to get the individual scheduled processes. It does not spell out when-not-to-use or contrast with buscar_entidades/buscar_acf, but the follow-up alternative is named.

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