Buscar el calendario de publicaciones 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 the safety profile is covered structurally. The description adds that the calendar is 'forward-looking' and summarizes the returned fields, but says nothing about result volume, pagination behavior, or data coverage limits beyond what annotations and schema already convey.

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 short clauses, no filler, and the resource identity is front-loaded before the parameter hint. It is efficient, though the trailing solo_proximas sentence adds little beyond the schema.

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, return-value explanation is not required, and 100% schema coverage documents every parameter. The description gives enough for an agent to identify the dataset and its field set; the missing piece is comparative guidance against sibling BCE search tools.

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 100% across all 9 parameters, so the schema fully documents dates, limit, offset, query, format, categoria and periodicidad. The description only echoes solo_proximas, which the schema already explains — baseline 3 when the schema does the heavy lifting.

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 precisely — BCE's forward-looking statistical release calendar — and enumerates what it returns (dates, category, periodicity, reference period). It distinguishes itself from sibling BCE tools like search_bce_publicaciones or search_bce_indicadores by being explicitly a release-calendar tool, though it never names those siblings as 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?

No when-to-use guidance and no routing to or away from alternatives among the many search_bce_* siblings. The only conditional hint is 'solo_proximas=true keeps upcoming releases', which is usage-flavored but restates the parameter's own schema description rather than advising the agent on whether to pick this tool.

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