get_stock_quote

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

Since there are no annotations, the description must carry the behavioral burden. It provides critical operational context by labeling the source as 'Yahoo Finance (unofficial)' and warning about 'may be delayed,' which is vital information for the agent.

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 definition is highly efficient; both sentences serve a distinct purpose—the first defining functionality, the second defining operational constraints—and are placed front-loaded for maximum impact.

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?

It is highly complete for a lookup function, covering the goal, the scope (NSE/BSE), and the data quality caveats (unofficial/delayed). It achieves a high standard of usability without being verbose.

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?

With 0% schema description coverage, the description must explain parameters. It successfully defines the purpose of 'symbol' and 'exchange' by providing concrete examples of what values are expected and how they relate.

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 is extremely clear, stating the specific action ('Latest price'), the resource ('NSE/BSE stock'), and providing a concrete example ('RELIANCE' on 'NSE') to ground the intent.

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 by detailing the necessary inputs (symbol and exchange) and an example, but it does not explicitly state when to use this tool over alternatives like 'get_index_quote' or 'get_stock_history' among the siblings.

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