Get ABS data

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

With no annotations, the description carries the full burden and does add one real behavioral trait: an empty/wide key can return thousands of series, a large-response warning. It says nothing about auth, rate limits, pagination, or the return shape, so for an unannotated data tool it remains only partially transparent.

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 sentences, front-loaded with the core fetch action, then the key-narrowing warning, then the last_n tip. Nearly every sentence earns its place; only the dataflow-parameter provenance could be tightened.

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?

Covers the essential key-usage and last_n semantics for a 5-param fetch tool, but with no annotations and no output schema, it omits the return format and result shape that an agent would need to consume the response, leaving a gap.

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 80%, so the schema already documents key, start, end, and last_n. The description reinforces the key-narrowness constraint and the last_n shortcut but adds no format/syntax detail beyond what the schema provides, matching the baseline-3 case.

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 (Fetch) and resource (any ABS dataflow) and ties the SDMX key to the sibling tool abs_describe_dataflow, which helps distinguish it from abs_search_dataflows and the specialized get_cpi/get_labour_force tools. Clear, though it doesn't explicitly say why to prefer it over the specialized siblings.

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 practical guidance ('Keep keys narrow', 'Use last_n to just get the latest values') and warns that an empty key on a big dataflow returns thousands of series. However, it never states when to use this generic tool versus the purpose-built siblings (get_cpi, get_cash_rate, etc.), leaving that routing to inference.

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