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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: NSE prices can lag the exchange by up to ~15 minutes, which matters for interpreting results. It stops short of describing response shape or failure behavior.

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 compact sentences: alias mapping, freshness caveat, and a concrete call example. Everything is front-loaded and nothing is wasted.

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 alias of a quote tool with full schema coverage and a complete annotation set, the description gives enough to call it and interpret staleness. No output schema exists, but the pointer to get_stock_quote's fields compensates adequately.

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 100%, so the symbol/ticker/identifier aliasing is fully documented in the schema. The description only repeats a usage example ({"symbol":"RELIANCE"}), adding minimal meaning beyond what the schema already 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 identifies the tool as an alias of get_stock_quote and names the fields returned (price_basis, last_trade_date), which lets an agent link it to the sibling that defines its behavior. It never states the purpose in its own words ('get a live stock quote'), so the agent must resolve the reference, but the mapping is unambiguous.

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?

Saying it is an alias with 'same fields' implies it is interchangeable with get_stock_quote, and the ~15-minute NSE lag note gives a data-freshness caveat. It does not say when to prefer this tool over get_stock_quote or any other quote source, leaving the choice implicit.

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