Buscar Licitaciones

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: default to current day, auto 30-day range, and valid states. However, it does not explicitly state read-only nature or rate limits, but given the search context, it is sufficiently transparent.

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 a single dense paragraph but front-loaded with core purpose. Each sentence provides essential information. Could be slightly more structured (e.g., bullet points) but overall concise and efficient.

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 6 parameters, no required ones, and no output schema, the description covers behavior, defaults, and enumerations well. However, it lacks information about pagination, result limits, and the format/mapping of output fields, which would be helpful for a search tool.

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%, but the description adds significant meaning beyond individual parameter descriptions: it explains state value meanings, the automatic 30-day behavior, and the relationship between fecha, codigoProveedor, codigoOrganismo, and nombreOrganismo. This adds value beyond the schema.

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 it searches licitaciones on Mercado Público (ChileCompra). It implicitly differentiates from sibling tools by specifying single-day default and filtering behavior, but does not explicitly name alternatives.

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?

Provides clear guidance on default behavior (today's results), filtering options (date, status, supplier, organization), and automatic 30-day search when no date is given with organization/supplier. Does not explicitly exclude other tools or mention when not to use.

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