get_macro_data

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. Description adds context about data type (GDP, CPI, PMI) and that indicator_code comes from list_macro_indicators, but does not disclose additional behavioral traits beyond annotations.

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?

Well-structured with strategy, critical rules, examples, and args sections. Front-loaded with purpose. Relatively concise, though some redundancy in listing args after the description.

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?

Tool has 5 parameters with output schema present. Description covers key parameters but omits count and offset (pagination). Given complexity, the description could be more complete to guide agent usage, especially for non-required parameters.

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%, so description carries full burden. It describes indicator_code ('From list_macro_indicators'), start, and end (both optional with date format), but does not explain count and offset parameters. Provides partial value, not fully compensating for missing schema descriptions.

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?

Description clearly states it retrieves macro indicator history (GDP, CPI, PMI), distinguishing it from sibling list_macro_indicators which lists available indicators. Provides verb+resource and examples.

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?

Explicitly instructs to call list_macro_indicators first to obtain indicator_code, and mandates that indicator_code must come from that source. This provides clear when-to-use context and necessary prerequisites.

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