Macro Indicator Data

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds useful behavioral context beyond annotations, such as pagination support (offset/limit) and the date format requirement (YYYY-MM-DD), which aids the agent in using the tool correctly.

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 concise with two sentences, providing essential information without unnecessary words. It is front-loaded with the purpose and then details the key parameters.

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?

Given the presence of an output schema and well-documented parameters, the description is complete enough. It covers the main purpose, data source, date format, and pagination, but does not mention return format details (handled by output schema).

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 coverage is 100% with parameter descriptions. The description adds context about date format and pagination, which while present in schema, reinforces the usage pattern. This is slightly above the baseline of 3.

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 verb 'Get' and the resource 'historical observations for one macro-economic indicator'. It distinguishes itself from the sibling tool 'macrodata_indicators' by specifying it retrieves data for a single indicator, not the list of indicators.

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 instructs to use 'indicator_code from macrodata_indicators', providing a clear prerequisite. It does not explicitly state when not to use, but the context is clear enough for a data retrieval tool with a sibling for listing indicators.

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