bls_series_data

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

Annotations declare readOnlyHint=true, which is consistent. The description adds that it returns monthly/quarterly/annual observations and lists popular series, but it does not mention rate limits, authentication requirements, error handling, or the response structure. The date range constraints are only in the schema parameter descriptions, not the main tool description.

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 concise and well-structured: a clear purpose statement followed by a bulleted list of popular series IDs and prefix explanations. Every sentence provides useful information without redundancy.

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 the complexity of BLS data and the absence of an output schema, the description should explain the return format (e.g., JSON fields) and mention any authentication or API key requirements. It does not cover these, leaving agents with incomplete information for correct tool invocation.

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 input schema covers 100% of parameters with descriptions. The tool description adds value by providing popular series IDs and explaining series ID prefixes, which aids in parameter usage. The schema already includes examples, so the description is helpful but not critical.

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 fetches time series data from the BLS and lists popular series IDs and prefixes. However, it does not explicitly differentiate from sibling tools like bls_employment_by_industry or bls_cpi_breakdown, which could be used for more specific BLS queries.

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 provides examples of when to use specific series IDs (e.g., CES for employment, CU for CPI) and implies it is the general BLS series data tool, but it lacks explicit guidance on when to use this tool versus alternatives on the same server.

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