get_stock_quote

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

With no annotations, the description carries the full behavioral burden. It only lists the returned data fields and does not disclose whether the quote is real-time or delayed, whether authentication is required, how invalid symbols are handled, or that this is a read-only operation.

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?

One compact sentence that front-loads the core purpose and follows with a clearly structured list of return fields. Every word earns its place; 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?

Despite having no output schema, the description clearly enumerates the return values, which is the main contextual gap. It remains short of complete because it omits symbol format and error behavior, but for a simple one-parameter read tool it is adequate for selection and basic invocation.

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 description adds 'NSE symbol' context that the schema lacks, and schema coverage is 0%, so some compensation is needed. But it does not specify symbol format, case sensitivity, or examples, leaving the agent to guess how to supply the symbol.

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?

States a specific verb and resource: retrieving the latest quote for an NSE symbol, then enumerates the exact data fields included. This clearly distinguishes it from siblings like get_price_history, get_key_ratios, or get_top_movers.

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?

Implies when to use it: whenever a current NSE quote snapshot is needed. However, it provides no explicit when-not-to-use guidance or alternatives, leaving the agent to infer distinctions from sibling names.

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