buscar_catalogo

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

With no annotations, the description carries the full behavioral disclosure burden. It accurately indicates a read-only catalog search and the level of the taxonomy, but it does not explain whether searches are exact or partial, whether codigo and nombre are alternatives or combinable, or what pagination behavior to expect.

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 with no filler, front-loading the action and resource before listing the search keys. Every word contributes to understanding the tool's 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?

The description captures the core purpose but omits invocation details such as whether at least one search key is required and the role of categoria/pagination parameters. The presence of an output schema reduces the need to document return values, but agent invocation guidance remains partially under-specified.

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 covers 'codigo' and 'nombre' as search keys but remains silent on 'categoria', 'pagina', and 'items_por_pagina', leaving those roles to be inferred from names and defaults.

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 uses a concrete verb ('Busca') and a specific resource ('productos del catálogo de bienes y servicios (nivel 5)') and names the search criteria ('por nombre o código'). This clearly differentiates it from sibling search tools like buscar_procesos and buscar_proveedores.

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 implies when to use the tool: when searching catalog products by name or code. It does not explicitly state exclusions or alternatives, but the resource-specific wording makes the use case clear enough.

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