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

With no annotations, the description must carry the full burden of behavioral disclosure. It lists output components (regime, trend, percentile, ranked actions) but does not explicitly state that the tool is read-only, has no side effects, or requires any permissions. It also fails to mention any limitations, rate limits, or data source caveats, leaving the agent with an incomplete picture of the tool's behavior.

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 a single, information-dense sentence that front-loads the core purpose ('CPI YoY') and then details the interpretation layer. The phrase 'Built for autonomous agents' is somewhat redundant with the 'AGENT-NATIVE' tag, but overall the structure is efficient and avoids unnecessary verbosity.

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 tool's complexity and the absence of an output schema, the description does list the key output fields (regime, trend, percentile, ranked actions), which is helpful. However, it lacks context on the data source, update frequency, and how it relates to other inflation tools. In a landscape with multiple inflation siblings, the description is insufficiently complete for an agent to make an informed choice.

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 tool has zero parameters, and the schema is empty with 100% coverage. Per the baseline for no parameters, the description need not explain parameter semantics. It correctly provides no parameter information, and this does not detract from its value.

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 identifies the tool as providing CPI YoY data with an interpretation layer, distinguishing it from raw inflation tools. While it lacks an explicit verb like 'retrieve' or 'get', the intent is evident from the context, and the mention of 'regime', 'trend', and 'ranked actions' specifies what is offered.

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?

There is no explicit guidance on when to use this tool compared to sibling tools like bls_inflation or inflation. The phrase 'Built for autonomous agents' hints at a target audience but does not provide criteria for selection or mention alternatives. The description lacks any exclusions or recommendations.

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