buscar_bomes

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

With no annotations, the description carries full behavioral burden and does so well: pagination (10 per page), default date range (2014-01-01..today), case/accent insensitivity, AND-only termino semantics, and the site's OR-ignoring quirk are all disclosed. It also clarifies the difference between sumario and contenido scopes.

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 dense but well-organized, front-loading the purpose and return type. It packs many constraints and alternatives into a compact block; bullet formatting could improve scannability, but no sentence is wasted.

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 13 parameters, no annotations, and no output schema, the description covers purpose, parameter semantics, date defaults, filters, and sibling alternatives thoroughly. It does not describe the output format beyond 'BOLETINES (10 por página),' but that may be sufficient 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 description coverage is 0%, so the description compensates by explaining key parameters: texto, ambito, terminos, date formats, and filter categories (IDs and exact numbers). It doesn't enumerate every parameter individually but gives enough for correct invocation, including the shape of terminos objects.

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 opens with 'Búsqueda en vivo en el buscador avanzado del sitio: devuelve BOLETINES', clearly identifying the action (search) and resource (bulletins). It explicitly differentiates itself from article-level tools by noting 'Para ver qué artículos coinciden usa buscar_articulos o buscar_en_indice.'

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 explicit routing guidance: 'el sitio ignora el O, así que se rechaza (usa buscar_articulos)' and 'Para ver qué artículos coinciden usa buscar_articulos o buscar_en_indice.' Also references listar_consejerias/listar_organismos for ID filters and notes the ambito scope for 2014-2016 content.

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