get_inflacion_ytd

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

No annotations are provided, so the description carries full burden. It does add the useful basis of calculation ('UDIS 1-ene a hoy'), implying a read-only, single-value snapshot, but it never states the return unit (percentage vs. index) or format. Adequate but incomplete for a description with zero structured behavioral support.

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 bilingual lines that are front-loaded and easy to scan. The phrase 'en un clic' is mild marketing filler that doesn't add informational value, preventing a 5.

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 no output schema and no annotations, the description should clarify what the caller actually receives (e.g., a percentage figure for the year to date). It states the concept and window but leaves the returned value's form implicit, which is a real gap for a zero-param call with no schema to fall back on.

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 takes zero parameters, so per the rubric the baseline is 4. No parameter semantics are needed or missing.

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 a specific verb+resource ('Inflacion acumulada del anio' / year-to-date inflation) with a concrete calculation window (UDIS 1-ene a hoy), so the resource is unambiguous. However, it does not distinguish itself from close siblings like get_inflacion_udis or get_expectativa_inflacion, leaving the agent to infer how this differs.

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 only asserts what the tool returns; it gives no when-to-use context, no prerequisites, and never names the alternative tool for a different inflation view. The agent must guess between get_inflacion_ytd, get_inflacion_udis and get_expectativa_inflacion on its own.

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