Get live quotes

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 reveals that quotes are 'live,' that scrip codes follow a specific format, and that mode='ltp' returns only last traded price. However, it does not describe the response shape, what 'full' mode includes, error behavior, or any side effects—though this appears to be a read-only quote tool.

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?

Three short sentences, each contributing useful information: purpose and format, prerequisite workflow, and mode semantics. No filler or repetition; the most important operational detail (code format) is front-loaded.

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 quote-fetching tool with no output schema, the description provides enough to call it correctly: scrip code format, prerequisite lookup step, and mode behavior. It does not describe the returned payload or error handling, but the core usage is adequately covered.

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 schema documents only an example for scripCodes and an enum for mode (50% coverage), so the description adds meaningful semantic value. It explains the scrip code format and what mode='ltp' does, covering both parameters beyond what the schema alone provides.

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 'live market quotes' for scrip codes and specifies the required format (e.g., 'NSE_2885'). It is specific about the resource and action, though it does not explicitly distinguish itself from closely related siblings like stream_quotes or watch_prices.

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?

It gives explicit workflow guidance: 'Use search_instruments first to get scrip codes' and 'Set mode='ltp' for last traded price only.' This is clear practical context, but it does not state when not to use this tool or suggest an alternative sibling for streaming or historical needs.

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