Rbi Get Policy Rates

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

With no annotations, the description carries the full burden. It does state that the result includes an as-of date, which is useful behavioral context. However, it does not disclose whether the data is cached, how frequently it updates, or any rate limits—modest behavioral detail overall.

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, front-loaded sentence with zero filler. Every word contributes to understanding the tool's scope.

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?

The description is complete for a simple, no-parameter tool; together with the output schema it gives the agent enough to invoke and interpret results. It could be improved by noting data sources or update frequency, but nothing essential is missing.

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 no parameters and no schema to document them, so the baseline is 4. The description mentions the set of rates returned, which is somewhat informative about the output, though the output schema already covers return 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 states a specific verb (Get) and resource (current RBI policy rates), and enumerates the exact rate types (repo, SDF, MSF, bank rate, CRR, SLR), which clearly distinguishes this tool from all GST, income tax, MF, and NSE siblings.

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 by the name and description, but there is no explicit when-to-use or when-not-to-use guidance, nor mention of alternatives. For a zero-parameter, single-purpose tool this is acceptable but not ideal.

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