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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context with the data source (World Bank CPI), pricing ($0.008 per call), and HTTP method (GET), but it does not disclose return format, error behavior, or how missing optional parameters are handled. Given the annotations, this level of added context is acceptable but not exceptional.

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 compact sentence that leads with the core function, followed by three concise clauses for source, pricing, and endpoint. Every element provides useful information with zero redundancy. This is appropriately front-loaded and efficient.

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 simple calculator with rich annotations and 100% schema parameter coverage, the description covers the essential function, scope, source, and cost. However, since there is no output schema, the description does not explain what the tool returns (e.g., adjusted amount as a number, a table, or additional metadata). Without any return-value information, an agent may be uncertain about how to interpret the response.

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 100%, so the baseline is 3. The main description's phrase 'Adjust an amount between years' loosely maps to the `from`, `to`, and `amount` parameters but does not add syntax, format, or default details beyond what the schema already provides. The per-parameter descriptions in the schema carry the semantic load.

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 states a specific verb and resource: 'Adjust an amount between years using CPI.' It also clarifies scope ('any country, not just US') and data source (World Bank CPI), which distinguishes it from related tools like v1_fx or v1_unit_convert. The title 'Inflation calculator' reinforces the purpose, creating a clear, unambiguous definition.

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 implies when to use this tool (adjusting monetary amounts for inflation using CPI) and the 'any country, not just US' note adds useful context, but it does not explicitly mention alternatives or exclusion cases such as 'for currency conversion use v1_fx instead.' Usage guidance is present by implication rather than explicit routing.

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