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

With no annotations, the description carries the burden of behavioral disclosure. It lists the fields included and indicates a read-only snapshot, which is good. However, it does not mention potential caveats like data delays, market hours, or symbol normalization, leaving some ambiguity for a real-world quote tool.

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 a single, tightly packed sentence that conveys all essential elements without fluff. It is front-loaded with the core purpose and uses an em-dash list for fields, making it very readable.

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 one-parameter tool with an output schema, the description is largely sufficient. It states the tool's purpose and return fields. However, the lack of symbol format guidance and any usage caveats, combined with low parameter semantics, leaves a small gap. Still, overall completeness is high given the tool's simplicity.

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 schema has a single 'symbol' parameter with no description, and schema description coverage is 0%. The description only says 'NSE stock', implying the symbol is for NSE, but doesn't specify format (e.g., 'RELIANCE' vs 'RELIANCE.NS') or any validation rules. The description adds minimal value beyond the schema.

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 uses a specific verb 'snapshot' and identifies the resource as 'NSE stock', listing the exact fields returned (last close, prev close, change %, day H/L, volume). This clearly distinguishes it from siblings like get_ohlc_data (historical data) and get_technical_indicators (indicator calculations).

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 phrase 'Latest price snapshot' implies this tool is for current market data, contrasting with historical or analytical tools. However, there is no explicit statement of when to use this versus alternatives, nor any exclusions. The context is clear but not fully spelled out.

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