Catálogo de series populares del Banco Central

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

The description adds behavioral context beyond the readOnlyHint annotation by noting it is 'local (sin red ni clave)'—meaning no network or credentials are required, and it runs locally. It also implies the catalog is a static list rather than a live query. There is no contradiction with annotations.

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 two sentences with high information density: it states the purpose, gives examples, and provides actionable guidance in the second sentence. No fluff 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?

For a no-parameter tool with an output schema, the description fully covers what the agent needs to know: what the catalog is, what it contains, where to find the full catalog, and how to verify codes. The output schema handles return format, and annotations handle safety, so nothing is missing.

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?

The tool has zero parameters, so the baseline is 4. The description adds context by enumerating the types of series included (inflation, rates, GDP, unemployment), which helps the agent understand the scope of the catalog, even though no parameter details are needed.

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 the tool as a 'Catálogo local de las series más usadas de la BDE' (local catalog of the most used BDE series) and lists concrete examples (UF, UTM, IPC, TPM, exchange rate, IMACEC, GDP, unemployment). It distinguishes itself from siblings by emphasizing the 'local' and 'popular' nature, and by pointing to the full catalog elsewhere.

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 explicitly states when to use the tool (for a quick local list of popular series without network/key) and when to use alternatives: the complete catalog is available at si3.bcentral.cl/Siete, and code verification should be done with bcentral_serie_info. This provides clear contrasts with sibling tools and external resources.

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