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

With no annotations provided, the description carries the full burden. It states the tool provides real-time and historical data, implying a read-only operation, but does not disclose response format, pagination, rate limits, or any other behavioral traits. It is adequate but not rich.

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 two sentences, front-loaded with the core function and followed by a brief use case. There is no redundant filler or unnecessary detail, making it highly 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?

The tool has no output schema and no annotations, so the description should compensate by explaining what the response looks like or how to construct the indicator name. It gives examples but does not describe return values or behavior when optional date parameters are omitted, leaving some context incomplete for agents.

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 schema already documents all parameters (name, from, to). The description adds examples of indicator names (GDP, unemployment, inflation), which helps clarify the 'name' parameter, but does not go beyond the schema's basic meaning.

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 clearly states the tool accesses real-time and historical economic data for key indicators such as GDP, unemployment, and inflation. It is specific about the resource and purpose, though it does not explicitly differentiate from closely related siblings like getTreasuryRates or getEconomicCalendar.

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 provides a general use case ('measure economic performance and identify growth trends') but gives no guidance on when to use this tool versus alternatives, nor any exclusions. There is no mention of sibling tools or scenarios where a different economic data tool would be more appropriate.

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