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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — no indication of what the series data contains, granularity, pagination, or typical response size — only a procedural pointer to describe_operation.

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, so half the text is waste rather than information. Brevity here reflects under-specification rather than disciplined conciseness.

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?

For a tool with a nested, fully unconstrained query object and no output schema, the description leaves the agent unable to construct a call without first invoking describe_operation. Delegation to describe_operation is a legitimate pattern, but nothing here even states that calling it is required before this endpoint can be used.

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 the 'query' parameter is a free-form object with additionalProperties: {}, so the schema gives the agent essentially nothing about what query keys are accepted. The description does not compensate at all, offering only the generic instruction to consult describe_operation rather than naming any parameter, filter, or format.

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 consists of the endpoint path repeated twice, which effectively restates the title 'economic-data: GET /api/economic-data/cpi/series' without saying what a CPI series is or what the endpoint returns. It is marginally distinguishable from siblings such as get_economic_data_cpi_history or get_economic_data_cpi_current only by the word 'series' in the path, not by any explanatory verb+resource statement.

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 endpoint versus the other CPI siblings (current, history, annual_change, calculate), which is the main selection problem an agent faces here. The only actionable guidance is the pointer that 'describe_operation provides native request schemas', which helps with invocation but not with tool selection.

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