Precios de combustibles de ANCAP

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context: prices are IVA-inclusive and administratively fixed by the Executive, and the catalogue-first pattern constrains how `producto` may be populated.

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?

Three short lines, zero filler, and the price definition is front-loaded before the parameter behavior. Every clause maps to a distinct decision the caller has to make.

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?

An output schema exists, so return values need no explanation, and the description covers the catalogue/query branching completely. Only the integer format of `anio` and `mes` is left implicit, which is a minor omission for a zero-required-parameter 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 coverage is 0%, so the description carries the full burden, and it does explain the role and interaction of all three parameters (catalogue mode vs. series mode vs. single-month mode). It does not state formats or ranges for `mes`/`anio` (e.g. 1-12, four-digit year), leaving a small gap.

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 resource and scope: maximum retail prices (IVA included) for ANCAP fuels as fixed by the Executive. This clearly separates it from siblings like ventas_combustible (sales volumes) or paridad_combustibles (parity), though those siblings are never named explicitly.

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?

Gives explicit conditional usage for every mode: with no `producto` you get the product catalogue, with `producto` you get the monthly series, and adding `anio`+`mes` narrows to one month. It also warns that the names returned by the catalogue must be passed verbatim — the exact trap an agent would otherwise fall into.

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