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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only lists data categories without explaining the return format, time range, data source, or whether the data is historical or current. This leaves the agent uncertain about the tool's actual behavior when invoked.

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 sentence that efficiently captures the tool's content with no filler. Every phrase adds value, making it an appropriately sized and front-loaded description.

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 description provides a reasonable high-level overview, but it omits details such as whether it returns historical series, current values, or a specific time period. With no output schema or annotations, this leaves gaps in the agent's understanding of the tool's full behavior.

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 contains no properties, so schema coverage is trivially 100%. The description adds no parameter details, but none are necessary for a parameterless tool; the baseline of 4 applies.

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 what the tool provides: US inflation data including CPI, PCE, core inflation, and YoY/MoM changes. It specifies a clear resource (US inflation) and scope, but does not differentiate it from overlapping siblings like bls_inflation or inflation_v2, so it stops short of a 5.

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 offers no guidance on when to use this tool versus alternatives such as bls_inflation or inflation_v2. It does not mention any exclusions, alternatives, or prerequisites, leaving the agent with no decision criteria for tool selection.

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