explore_bls_metrics

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

With no annotations, the description carries the burden. It implies a read-only discovery behavior and provides filter categories and source enumerations, adding useful context. However, it does not disclose whether results are paginated, limited, or how search semantics work (e.g., exact vs partial match).

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 focused sentences, front-loaded with the main purpose and immediately followed by usage guidance and parameter details. Every sentence earns its place; no filler.

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 a simple exploration interface with three optional parameters and an output schema to cover return values. The description explains purpose, when to use, and parameter values, making it sufficiently complete for onboarding. Minor gap: no mention of list size or examples, but not essential.

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 0%, but the description compensates by explaining the query parameter as 'search by name' and enumerating valid values for category ('employment', 'wages', 'derived') and source ('ces', 'qcew', 'oews'). This adds meaning beyond the bare property names.

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 uses a specific verb 'Discover' and names the resource 'available BLS metrics and what data the API offers.' It clearly distinguishes this exploration tool from sibling tools like 'explore_census_metrics' and 'explore_sba_metrics' by naming BLS and labor market data.

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?

Explicitly states to use it 'before making specific queries' to understand available data, providing clear usage context. It does not explicitly list alternatives or when not to use it, but the guidance is strong enough for an exploration tool.

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