Listar indicadores diarios y mensuales del BCE

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new context — the temporal depth (riesgo país daily since 2004) and the breadth of series — but says nothing about pagination, ordering, or how widgets are keyed for the follow-up call.

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?

Two compact sentences: the resource and its scope lead, the actionable next-step trails. No filler. Minor cost is that the series enumeration, while informative, is fairly dense.

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?

With an output schema present and read-only annotations, the description need not explain return values, and it adequately covers scope. The gap is the crowded sibling landscape of BCE indicator tools, where the definition does not make the selection boundary explicit.

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 single 'format' parameter has an enum and a complete schema description (100% coverage), so the schema carries the semantics. The description adds no format or syntax guidance, which is the expected baseline when coverage is this high.

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?

States the resource (BCE daily and monthly indicator widgets) and enumerates the concrete series covered (riesgo país since 2004, gold, WTI, bonds, payments, reserves, fiscal/external). It distinguishes itself from BCEData and points at the sibling get_bce_indicador_diario, so an agent can place it in the BCE family without opening the schema.

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 'Next: get_bce_indicador_diario' hint implies the list-then-fetch workflow, which is useful routing. However, it never states when to prefer this over the nearby siblings search_indicadores_bce, get_indicador_bce, or list_sut_indicadores, leaving the choice to inference.

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