fyers_live_quote

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

With no annotations, the description carries the burden. It discloses 'zero delay when configured' as a behavioral trait, lists returned fields, and implies a read-only operation. However, it doesn't mention error behavior or data freshness guarantees beyond zero delay.

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 concise with a purpose sentence, output list, setup instructions, and parameter details. The setup section is slightly detailed but may be extraneous if the environment is already configured. Overall, no wasted sentences.

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 an output schema exists, the description covers main return fields and setup. It lacks information on error handling, rate limits, or symbol validation, but for a simple live quote tool, it is mostly complete.

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 input schema has 0% description coverage, but the description provides parameter meaning: 'symbol: NSE symbol (e.g. RELIANCE, TCS, INFY)'. This adds clarity beyond the schema's type-only definition, though it could include more examples or accepted formats.

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 stock quote via Fyers API v3' with specific output fields (LTP, O/H/L/C, volume, change%, 52W high/low). It distinguishes from siblings by specifying the Fyers API source, which sets it apart from other live quote tools like nse_quote or stock_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?

The description implies usage for NSE stocks via Fyers but does not explicitly state when to use this tool versus alternatives (e.g., nse_quote, bse_quote). No guidance on when not to use or prerequisites beyond setup credentials.

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