india_gsec_yields

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

No annotations are provided, so the description must disclose behavior. It lists what data is provided and mentions live data source links, but does not specify data freshness, calculation methodology, or potential delays/latency. It also doesn't mention whether the output is cached or request-time fetched.

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 structured with a header, justification, bullets, and example, but the Bloomberg price comparison sentence is not directly useful for agent invocation. It adds context on why the tool exists but isn't concise. The core data list is efficient.

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, single-purpose tool with an output schema, the description is fairly complete. It enumerates exact maturities and provides source links, which sets expectations. It doesn't explain return formatting, but the output schema covers that.

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?

Tool has zero parameters, and schema coverage is trivially 100%. Description includes a call example, confirming no args needed. No parameter explanation is necessary.

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 provides India G-Sec yields from 91-day T-bill to 30-year bond, listing specific maturities. It lacks an explicit imperative verb like 'fetches' but is unambiguous. It doesn't explicitly distinguish from sibling rbi_policy_rates, though the focus on yield curve is clear.

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 gives context that RBI/CCIL are free sources vs Bloomberg, implying this is the low-cost way to get bond yields. However, it does not state when to use this vs alternatives like rbi_policy_rates or india_macro_indicators, nor any exclusions. Usage guidance is only implicit.

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