List known BoE IADB series

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

No annotations are present, so the description carries the burden. It openly discloses the curated nature (not exhaustive) and that get_series accepts more codes, setting correct expectations about coverage and scope.

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?

Two sentences, front-loaded with the verb and outcome. Every clause adds value—scope, fields returned, usage intent, and alternative. 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?

The tool is simple (list operation, no params) and the output schema exists. The description covers purpose, output fields, scope limitations, and relationship to sibling tools, making it fully complete for an agent.

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 zero parameters, so the schema is empty and no parameter-specific guidance is needed. The description effectively explains the output, which is the sole input-agnostic behavior.

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 lists a curated catalog of BoE IADB series with specific fields (code, name, description, unit, frequency). It also distinguishes itself from siblings like get_series by explicitly noting its role in discovering codes.

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?

It explicitly says 'Use this to discover series codes to pass to get_series' and notes that get_series accepts any IADB code, not just these. This gives clear when-to-use guidance and alternative behavior.

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