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

With no annotations, the description carries the full load and does disclose real behavior: first-release vs latest value with a revised flag, surprise methodology (market-implied when a matching prediction market exists, else trend-model), and next release date. It also notes cost ($0.02 via x402) and HTTP method. Auth/rate-limit behavior is not covered, keeping it short of a 5.

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?

Front-loaded summary sentence followed by the payload breakdown; the bracketed HTTP/price/docs tag is useful metadata. Minor redundancy between the first two sentences ('Core CPI inflation ... latest print, revisions, surprise' restated as 'Latest Core CPI inflation print ...'), but overall efficient.

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?

No output schema and no annotations exist, yet the description enumerates the returned fields (revised flag, surprise vs labeled expectation, next release date, mini-series) well enough for an agent to know what comes back. Missing only the JSON shape detail that an output schema would normally supply.

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?

Zero parameters, so baseline 4 applies. The description correctly describes a no-argument, fixed-series endpoint rather than implying any filter or query options.

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 resource (Core CPI from BLS, via FRED/ALFRED) and the exact payload (latest print, revisions, surprise, next release, 12-observation series). The line 'Same shape as /v1/econ/:series bound to core-cpi' cleanly distinguishes it from the generic econ_series and the adjacent cpi/core-pce/pce-inflation siblings.

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 'bound to core-cpi' framing implies this is the series-specific variant of econ_series, so usage is inferable. But it never states when to pick this over econ_series_cpi (headline) or core_pce, nor any exclusions. Guidance is present but only implicit.

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