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

With no annotations, the description carries the behavioral burden. It conveys that this is a read-only real-time lookup and lists what it returns, but it does not disclose data freshness limitations, symbol coverage caveats, or error behavior for invalid tickers.

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?

A single sentence with no filler; the verb and resource are front-loaded and the listed outputs are specific and useful.

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 one-parameter lookup tool, the description tells the agent what to pass and what data it will receive. It lacks caveats around invalid symbols or coverage, but the simple scope does not demand much more.

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% and the schema already documents the single required parameter (symbol) with examples. The description adds only the general claim 'any ticker symbol,' which is marginal on top of 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 states a clear action ('Get') on a specific resource ('real-time stock price') and enumerates the returned fields (52-week highs/lows, PE ratio, volume, market cap). It is clearly a quote-lookup tool, but it does not explicitly differentiate itself from sibling tools like analyze_stock_ai or get_top_trade_ideas.

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 gives no guidance on when to choose this tool over alternatives. There is no mention of when a quick quote is appropriate versus deeper analysis or simulation, no prerequisites, and no stated exclusions.

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