get_ine_series_data

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

No annotations are provided, and the description offers no behavioral insights beyond the basic action. It does not disclose return format, pagination, authentication requirements, rate limits, or any side effects. For a data retrieval tool, this is insufficient.

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 a single sentence of few words, no redundancy. It is front-loaded with the main action. However, it could benefit from a more structured format to list key parameters or usage notes.

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 simple parameter set and no output schema, the description is too sparse. It does not explain what a 'series code' is, what 'time series data' looks like, or the source (INE). A more complete description would help the agent understand the tool's purpose and usage.

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%, with both 'series_code' and 'nult' having clear descriptions. The tool description adds no extra meaning beyond repeating 'by series code'. With full schema coverage, baseline of 3 is appropriate.

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 'Get time series data from INE by series code.' It uses a specific verb ('Get') and resource ('time series data from INE'), and the primary parameter 'series_code' is immediately understood. However, it does not explicitly differentiate from siblings like 'get_ine_table_data' or 'get_ine_operation', but the focus on 'series' makes it distinct.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or exclusion criteria. The description is a simple functional statement without context.

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