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 the safety profile is fully covered structurally. The description adds nothing beyond a pointer to describe_operation — no return shape, no calculation semantics, no parameter 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?

It is short, but the first two sentences are identical restatements of the URL path — pure duplication rather than front-loaded information. The only value-bearing content is the trailing note about describe_operation.

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 an opaque nested schema, no output schema, no parameter documentation, and many near-identical CPI siblings, the description omits everything an agent needs: what the calculation is, required inputs, and how to choose among alternatives.

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?

Two parameters exist (query and params) with 0% schema description coverage, and the schema is essentially opaque (additionalProperties, empty properties). The description supplies zero parameter meaning, leaving an agent with no way to construct a valid request without calling describe_operation.

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 just the endpoint path repeated twice ('GET /api/economic-data/cpi/calculate') plus an operation ID. It hints at a CPI calculation but never states what is being calculated, from what inputs, or how it differs from siblings like get_economic_data_cpi_current or cpi_annual_change.

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?

No when-to-use, when-not-to-use, or alternative is given. The only actionable pointer is 'describe_operation provides native request schemas', which is a discovery hint rather than selection guidance against the many other CPI endpoints.

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