india_macro_indicators

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

With no annotations provided, the description carries the full burden. It adds useful context about the World Bank source and lists the indicators, but does not disclose data freshness, update frequency, pagination, or any limitations. The example call shows zero parameters, which clarifies the invocation but is not a full behavioral profile.

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 clear and front-loaded with the tool's purpose, but includes a tangential pricing paragraph that, while providing context, is not essential for tool invocation. The list and example are well-structured, but the pricing info could be trimmed for the agent.

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 zero-parameter tool, the description adequately covers what data is returned, the source, and provides a usage example. The output schema exists to define return structure, so the description fills the semantic gap. It could mention potential missing indicators or update latency, but it's largely sufficient.

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?

The tool has zero parameters, so the description doesn't need to explain parameter semantics. The example call india_macro_indicators() explicitly confirms no arguments are needed, and the empty schema with 100% coverage leaves no ambiguity.

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 identifies the tool as surfacing India macroeconomic indicators, explicitly listing CPI, GDP, current account, unemployment, etc. It distinguishes from sibling tools like rbi_policy_rates by covering broad macro data, though the verb is implicit ('provides') rather than a direct action verb.

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?

No explicit guidance on when to use this tool compared to siblings. The pricing comparison with Bloomberg/Refinitiv is a rationale for using free World Bank data but not a usage guideline. It does not mention alternatives like rbi_policy_rates or india_gsec_yields or when to prefer them.

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