get_nse_quote

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

No annotations provided, so description carries full burden. Discloses API source (official NSE India REST API) and authentication requirement (no API key). Does not mention rate limits, latency, or error handling, but covers key data fields and source adequately.

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?

Extremely concise: one sentence stating purpose, followed by bullet list of key data fields, then one sentence on API source. No wasted words, front-loaded with main action.

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 tool with one parameter and no output schema, the description adequately covers purpose, available data fields, and source. Could mention output format or example response, but the listed fields give enough context for an agent.

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 schema description coverage 100%. Schema already explains that symbols are without .NS suffix and gives examples. Description adds no further parameter semantics beyond what schema provides, so baseline 3.

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?

Clear verb 'Get live NSE India quote' with resource 'NSE India exchange-specific data'. Lists distinct data fields (VWAP, circuit breakers, etc.) and explicitly distinguishes from other quote tools like get_quote and get_bse_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?

Specifies when to use: when exchange-specific data (VWAP, circuit limits, delivery ratio) is needed. Does not explicitly state when not to use or name alternatives, but the context of NSE-specific data implies its niche.

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