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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds nothing beyond those annotations except the name of a companion tool for schemas; it says nothing about response shape, date-range scope, or pagination of historical data.

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 first sentence is duplicated verbatim, wasting the only front-loaded opportunity. What remains is an operation ID and a pointer to another tool, with no substantive content.

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?

With 0% schema coverage, nested objects, and no output schema, this description leaves an agent unable to construct a call without first invoking describe_operation. The pointer to that tool is the sole redeeming element and prevents a 1.

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% and both parameters (a free-form 'query' object with additionalProperties allowed and an empty 'params' object) are undocumented. The description provides no parameter meaning at all, so an agent has no way to know what goes into 'query' without calling describe_operation separately.

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 is a bare restatement of the endpoint path, duplicating the title verbatim. It does imply retrieval of CPI history, which loosely distinguishes it from siblings like cpi_current or cpi_series, but it never explains what 'history' means versus those alternatives.

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 statement of when to use this over get_economic_data_cpi_series, cpi_current, or cpi_annual_change. The only quasi-guidance is the pointer that describe_operation provides native request schemas, which tells an agent how to get parameters but not when to pick this tool.

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