get_macro_indicators

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

No annotations provided, so the description carries full burden. It only states what data is returned, not behavioral traits such as data freshness, rate limits, or that it's a read-only operation. Minimal transparency beyond the basic function.

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?

A single, concise sentence with no wasted words. Front-loaded with the action and scope, followed by parameter options. Ideal for quick parsing.

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 single parameter and no output schema, the description covers the main purpose but lacks details on output structure, data granularity, or temporal coverage. It is functional but not fully complete for an agent to know exactly what to expect.

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 0%, so the description must compensate. It maps the enum values to real-world concepts (industry->credit/IIP, etc.), adding some meaning beyond the raw enum. However, it does not explain what each category returns in detail (e.g., time series or single values).

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 retrieves India macro indicators and lists specific categories (industry credit/IIP, demand GST/auto, GDP & trade). This distinguishes it from sibling tools like get_markets (market data) and get_sector_constituents (company data).

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?

Usage is implied: use when needing macro indicators. However, no explicit guidance on when not to use, prerequisites, or alternatives. The description could mention that this tool complements sibling tools like get_company_overview for micro-level data.

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