ine_indicator

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

With no annotations, the description must fully disclose behavioral traits, but it only says 'fetch' (suggesting read-only) and explains the 'T' placeholder for totals. It does not cover error handling, response format, required permissions, rate limits, or any side effects, leaving significant gaps for an agent.

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 plus an example, with no redundant text. It is front-loaded with the core action and code format. The example could be slightly cleaner (nested braces), but overall it is efficient.

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?

Given the lack of an output schema and the tool's complexity (nested dims object, multiple parameters), the description is incomplete. It does not explain what the response contains (e.g., a single value, a series, metadata) or how errors are indicated. This forces the agent to guess the return structure.

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 100%, so baseline is 3. The description adds meaningful context beyond the schema: it clarifies that varcd is exactly 7 digits, explains that Dim1 is the period, and introduces the 'T' convention for dimension totals. This helps the agent correctly construct the dims object.

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 states the tool fetches an INE statistics indicator using a 7-digit code (varcd) with dimension selectors. It specifies the exact resource and action, and the sibling tools (e.g., fuel_prices, weather_forecast) are in different domains, so no confusion arises.

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 gives an example of how to call the tool but does not explicitly state when to use it versus alternatives or when not to use it. The usage is implied by the domain, but there is no direct guidance on context or exclusions.

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