icici_live_quote

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

No annotations provided, so description carries the full burden. It discloses return values (LTP, O/H/L, previous close, volume, change%), real-time nature, and setup requirements including authentication and daily session token refresh. Missing details on rate limits or error handling, but overall strong.

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 clear purpose statement, return values, and setup instructions. The setup information is lengthy but still front-loaded. Some text could be considered extraneous for a tool description, but it remains efficient and informative.

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 tool has an output schema, return values are covered. The description provides sufficient behavioral context for a single-parameter real-time quote tool with authentication needs. Sibling tools are many, but the name and description make its niche clear.

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?

Only one parameter 'symbol' with 0% schema description coverage. The description compensates by specifying it expects an NSE symbol and provides examples (RELIANCE, TCS). This adds meaningful context beyond the schema's bare name. Could be improved by noting case sensitivity or format.

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 it provides 'Real-time NSE quote via ICICI Breeze API' and specifies 'zero delay when configured'. The tool name 'icici_live_quote' together with the description distinguishes it from siblings like nse_quote and fyers_live_quote.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for NSE real-time quotes via ICICI, but does not mention when not to use it or point to sibling tools like nse_quote or bse_quote.

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