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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds genuinely useful behavioral context: the supported instrument universe, the required symbol forms (BTC-USD, ^VIX), that it is a point-in-time snapshot rather than a series, and that some fields are conditional ('where they apply'). It omits data freshness/latency, which would have pushed this higher.

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?

Front-loaded with the field list, then coverage universe, then call format - a sensible order with no filler. The coverage enumeration is dense but each clause carries non-redundant information about what will and will not work.

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?

An output schema exists, so return values need no explanation, and the description still names the key fields and their conditional nature. What is missing for a snapshot tool with two optional parameters is the ticker-vs-instrument_id choice and the freshness of 'current' data.

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 baseline is 3, but the description adds format semantics the schema lacks: the -USD pair convention for crypto and ^VIX for the volatility index, which is the main way an agent would get a ticker wrong. It does not resolve the relationship between the two optional parameters (ticker vs instrument_id) or whether one is preferred.

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 (snapshot) and resource (one instrument) and enumerates the returned fields: price and recent changes, session state, 52-week range, market cap, sector, next earnings date. This clearly separates it from siblings such as get_price_history (time series) and get_technical_indicators (computed studies) without needing to open any schema.

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?

Gives explicit when-not-to-use boundaries ('Forex pairs, futures, options, other indices and non-US listings are not covered') plus the exact ticker forms for crypto and VIX. It does not, however, route the agent to any alternative sibling for the excluded asset classes, so the guidance stops one step short of full routing.

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