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

With no annotations available, the description carries the full burden for behavioral transparency. It discloses what the output contains (frequency, unit, source, licence for each series), which is helpful. However, it does not mention any such details as pagination, ordering, or potential limitations, though the simple nature of a list might not require them.

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 concise sentence, front-loaded with the verb and resource, and every phrase adds meaning (types of series and returned attributes). No wasted words.

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 that this is a parameterless list tool with no output schema and low complexity, the description adequately covers what the tool does and what it returns. It is complete for its intended purpose.

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 has no parameters, so the description does not need to explain parameter semantics. The baseline for 0 params is 4, and the description provides no irrelevant parameter information.

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 action ('List') and the resource ('high-frequency series catalog'), and specifies the types of series (rates, yields, monthly labour and energy) and the attributes returned (frequency, unit, source, licence). This distinguishes it from sibling tools like get_series_data (which likely fetches data) and search_indicators (which searches for indicators).

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 implies usage for browsing the catalog of high-frequency series when an overview of available series is needed, but it does not explicitly state when to use this tool instead of alternatives like get_available_indicators or search_indicators. No exclusions or alternatives are mentioned.

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