stock_quote

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Live quote' without explaining what data is returned, whether it is real-time or delayed, rate limits, or any other operational behavior. This is a significant gap for a tool expected to fetch dynamic market data.

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 one sentence, front-loads the key action ('Live quote'), and includes an example. Every word earns its place with no filler or repetition.

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 single-parameter tool with no output schema, the description covers purpose and parameter semantics. However, given the presence of sibling tools (e.g., stock_quote_fno, trade_info) and no annotations, it lacks guidance on return values, data freshness, or how it differs from similar tools. This makes it minimally viable but incomplete.

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% and the only parameter 'symbol' is described generically in the schema. The description adds meaning by specifying it as an NSE equity symbol and providing an example ('RELIANCE'), which clarifies the expected value. However, it could further explain case sensitivity or symbol format, so a perfect score is not warranted.

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 a 'Live quote' for an 'NSE equity symbol' with a concrete example ('RELIANCE'). It differentiates from sibling stock_quote_fno by specifying equity vs F&O, and the verb 'quote' despite being a noun conveys the action of retrieving a 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 implicitly conveys when to use this tool: for NSE equity symbols. The example 'RELIANCE' reinforces the equity focus, which distinguishes it from stock_quote_fno (likely for F&O). However, it does not explicitly state when not to use it or name any alternatives.

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