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

With no annotations present, the description carries full disclosure burden and delivers richly: it explains BLS rate limits, the shared-edge-IP cause, and — most valuably — that an upstream-limit error means BLS refused rather than that the series does not exist. This prevents an agent from misdiagnosing a common failure mode.

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 the series list, followed by the edge-case caveat. No filler — both sentences earn their place and the most important operational warning is placed at the end where it completes the picture.

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?

For a single-parameter tool with full schema coverage, the description is nearly complete: purpose, accepted values, availability guarantees, and error interpretation are all covered. The only gap is the lack of return format or units, which matters more because no output schema exists to fill it.

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 the input schema already documents the series parameter, including the five warm IDs and raw BLS ID acceptance. The description mirrors this and adds rate-limit nuance, which is behavioral rather than semantic, so the baseline 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 names a specific verb ('Get'), resource ('US economic time series from the Bureau of Labor Statistics'), and enumerates the five accepted series names. The US focus clearly differentiates it from the country-oriented siblings (compare_countries, country_indicator, country_profile).

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 clearly establishes context: use this for US BLS series, with the five warm series always available and raw IDs accepted under caveats. It does not explicitly name siblings or state when-not-to-use, but the US-versus-country focus plus the warm-cache distinction gives an agent adequate situational guidance.

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