buscar_proveedores

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not state that the operation is read-only, nor does it explain pagination behavior (limite, offset) or any required authentication. The description only implies searching without deeper behavioral context.

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 short (three sentences) and front-loaded with the main action. Each sentence adds information, though the second sentence ('Permite identificar...') is somewhat redundant with the first. Still, it remains concise and to the point.

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 has 6 parameters, no schema descriptions, and no annotations, the description is insufficient. It does not explain pagination, combining filters, or the output (though output schema exists, reducing some burden). The description leaves significant gaps for effective use.

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 only explains nombre, nit, and geographic location (departamento and ciudad loosely), but omits the pagination parameters 'limite' and 'offset'. Users must infer their purpose from names alone.

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 clearly states the tool searches for suppliers (proveedores) in SECOP II and lists specific search criteria (name, NIT, location). It differentiates from sibling tools that search contracts or processes, though it could be more explicit about the distinct resource type.

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 suggests use for verifying supplier registration ('Útil para verificar el registro de un proveedor'), but provides no guidance on when not to use it or how it compares to alternatives like buscar_por_persona or buscar_contratos_secop2.

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