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

Annotations already declare readOnlyHint and openWorldHint. The description adds important behavioral context beyond annotations: the data source (BLS), that results include 12-month change, and the x402 payment cost of $0.004 USDC per call. It does not cover rate limits or response format, but the payment requirement is a meaningful addition.

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?

A single tightly front-loaded sentence that names the source, the covered indicators, the fallback series option, and the cost. No filler or redundant explanation.

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 paid, read-only, open-world data query with no output schema and only half the parameters documented, the description covers the source, indicators, 12-month change, and cost. However, it omits defaults for start_year and points, how indicators and series interact, and what the response structure looks like.

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 50% (series and indicators have descriptions). The description largely repeats the same indicator list and notes any BLS series id is accepted, but adds no meaning for the undocumented points or start_year parameters and gives no syntax or default guidance.

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?

States a specific verb-resource pair: retrieves US labor and price statistics from the Bureau of Labor Statistics, covering named indicators and any BLS series id. This is clear but does not explicitly distinguish itself from siblings like labor_state or wages.

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?

No explicit when-to-use guidance, no when-not conditions, and no named alternatives such as labor_state, wages, or fred_series. Usage is only implied from the indicator list and BLS source.

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