icici_candles

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the source (ICICI Breeze) and enumerates interval options, but does not mention data freshness, coverage limitations, or any non-obvious behavior. It is not misleading, just minimal.

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 very concise and well-organized, with a clear one-line purpose, an interval options list, and an Args table. Every sentence adds value and there is no fluff.

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?

Given the simplicity of the tool and the existence of an output schema, the description covers essential information. It lacks explicit usage context and some behavioral details, but the core details (resource, intervals, parameters) are present. It is not exhaustive but sufficient for a straightforward data retrieval tool.

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 must compensate. It provides meaningful meaning for all three parameters: symbol is an NSE symbol with an example, interval has allowed values, and days has a default. This goes beyond the bare schema and helps the agent construct correct inputs.

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 resource as historical OHLCV candles from ICICI Breeze API, which is more specific than the tool name alone. It distinguishes from sibling tools like fyers_candles by naming the broker, though it lacks an explicit verb like 'retrieves' or 'fetches'.

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 guidance is provided on when to use this tool versus alternatives such as fyers_candles, stock_historical, or nse_historical. The description does list interval options and defaults, but it does not explain the intended use case or differentiation from similar tools.

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