get_candle_data

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

With no annotations, the description must carry the behavioral disclosure burden. It does not mention read-only nature, data availability limits, rate limits, pagination, or any other operational behavior. The interval and date-format notes are parameter help rather than behavioral transparency.

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 compact and front-loaded: one clear purpose sentence followed by essential format constraints. Every line earns its place with no wasted words.

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?

It covers the most error-prone parameters (interval and date format) and the output schema exists, so return structure is already handled. However, without guidance on exchange values or how symboltoken is obtained, an agent may still struggle to invoke the tool correctly.

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 description coverage is 0%, so the description's parameter notes add real value: it enumerates all valid interval values and specifies the exact fromdate/todate format with an example. However, exchange and symboltoken remain unexplained, leaving the agent to infer their meaning.

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 opens with 'Get historical OHLCV candle data,' which names a specific verb and resource. It is clearly distinguishable from most siblings, though it does not explicitly differentiate itself from get_nse_intraday_data or get_bse_intraday_data beyond the OHLCV term.

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 context is only implied: 'historical OHLCV candle data' suggests this is for past price data rather than real-time quotes or intraday-specific feeds. No explicit guidance about when not to use it or what alternatives to prefer is provided.

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