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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds nothing about what the response contains, freshness of the CPI figure, or any scoping constraints; it merely repeats the route.

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?

It is short, but the first sentence is duplicated verbatim, and the remainder is a pointer to another tool rather than front-loaded substance. Brevity here reflects under-specification rather than efficiency.

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 exists and the two undocumented parameters are left entirely unexplained, so an agent has no way to construct a correct call from this definition. For a tool with nested free-form input, this is wholly inadequate.

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 description coverage is 0% across two free-form nested objects ('query' with additionalProperties and an empty 'params'), and the description offers no explanation of what belongs in either. With parameters this opaque, the description must compensate and instead says nothing.

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 restates the endpoint path twice and never converts it into a plain-language verb+resource statement. An agent can infer it fetches the current CPI figure, but the description itself is essentially a tautology of the title, and it does not distinguish this from cpi_current siblings like cpi_history, cpi_series, cpi_calculate, or prime_rate_current.

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 guidance on when to use this tool versus the many other economic-data siblings. The only actionable sentence points at describe_operation for request schemas, which is a schema-lookup instruction, not usage guidance.

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