resumen_licitaciones

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

No annotations are provided, so the description carries the behavioral burden. It communicates that the operation is a filtered, minimal summary, which strongly implies a read-only query, and nothing suggests destructive behavior. However, it does not clarify how filters combine, what 'resumen' actually includes, or what happens when no filters are supplied.

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 one concise, front-loaded sentence: the core purpose comes first, followed by a compact enumeration of the optional filters. There is no filler or redundancy.

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 output schema exists and all parameters are optional, so the description conveys the basic operation and filter surface. However, with no annotations and a large set of sibling tools, it omits when-to-use guidance and leaves the distinction from counting and full-search tools implicit.

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 maps the five parameters into semantic groups: categoria, modalidad, comprador, and date range (desde/hasta). It does not specify date formats, allowed values, or how multiple filters interact, but the parameter names themselves are mostly self-explanatory.

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 identifies a 'minimum summary of licitaciones' and lists the main filtering dimensions, so an agent can tell what resource is being returned. It stops short of full distinction from siblings like buscar_procesos or contar_licitaciones, and it uses a noun phrase rather than an explicit action verb.

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?

There is no guidance on when to use this tool versus the many sibling tools such as obtener_licitacion, buscar_procesos, or contar_licitaciones. The optional filters imply a query-style use case, but no alternatives or exclusions are mentioned.

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