fyers_live_quote

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses setup prerequisites (pip package, env vars, credential URL) and notes 'zero delay when configured.' It also lists return fields. However, it does not describe failure modes, authentication errors, rate limits, or symbol validation behavior.

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 clear sections: what it does, what it returns, setup requirements, and arguments. Each sentence adds value and there is no fluff. The core purpose is front-loaded in the first sentence.

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 simple one-parameter quote tool, the description covers purpose, return data, setup, and parameter format. The presence of an output schema likely covers return structure. Missing elements include usage guidance relative to siblings and explicit error/edge-case behavior, but the description is largely complete for its complexity.

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 coverage is 0%, so the description must compensate. It defines the 'symbol' parameter as an NSE symbol with concrete examples (RELIANCE, TCS, INFY), clarifying the accepted format. It does not mention case sensitivity or exchange prefix, but the examples provide practical guidance.

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 real-time NSE stock quotes via Fyers API v3 and enumerates the returned fields (LTP, O/H/L/C, volume, change%, 52W high/low). However, it does not explicitly distinguish this from similar siblings like live_quote or stock_quote, relying on 'via Fyers API' as the only differentiator.

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 is provided. The description includes setup instructions but does not explain, for example, when to prefer this over nse_quote or icici_live_quote, or whether it is the only zero-delay option.

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