rbi_policy_rates

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

The description goes beyond the basic purpose by detailing exactly what data is returned (the six rates, stance, and action summary) and notes the data source (free from RBI vs. expensive Bloomberg data). It does not mention freshness or error handling, but no annotations are needed for a read-only data retrieval tool.

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 well-structured with a one-line summary, a bulleted list, and a usage example. The Bloomberg cost comparison is slightly tangential but brief and adds context. Overall, it is concise and front-loaded.

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 parameterless tool with an output schema, the description is complete: it names all included fields, provides an example, and explains the data source. It does not describe the exact output schema, but this is covered by the existing output schema structure.

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, and the input schema is empty, so there is nothing for the description to explain. The example `rbi_policy_rates()` confirms no arguments are required. Baseline 4 for zero parameters applies.

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 explicitly states 'Current RBI monetary policy rates' and enumerates the exact rates (Repo, Reverse Repo, CRR, SLR, MSF, Bank Rate) along with stance and last policy action. This leaves no ambiguity about the tool's purpose and distinguishes it from broader macro tools like india_macro_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 clearly signals when to use the tool—whenever current RBI policy rates are needed—and provides a concrete example. It does not explicitly exclude other tools or name alternatives, but given the specific subject matter, the usage context is clear.

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