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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read. The description adds concrete fields returned (price, open, range, change), but doesn't disclose additional behavioral traits like data freshness, timezone, or intraday session specifics. With annotations covering safety, a 3 is appropriate.

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 one short sentence, front-loaded with the main purpose, and includes all key fields. It's efficient, though it doesn't mention the sibling alternatives that could have been added.

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?

Given the tool is a simple quote fetcher with one well-documented parameter and readOnly annotation, the description is complete. The only minor gap is not specifying anything about data granularity or timing beyond intraday, but for this complexity it's adequate.

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%: the only parameter 'symbols' has a description with examples and a limit of 1-10 tickers. The schema already explains it fully, so the description adds no extra parameter semantics. Baseline 3 is correct.

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 clearly indicates it provides intraday quote data including price, open, daily range, and change from previous close. It's a specific resource (quote) and action (get), and while it doesn't explicitly name siblings like get_spot_price or get_price_series, the mention of intraday and change vs prior close differentiates it from general price series.

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 implies usage for intraday quote needs but doesn't explicitly state when to use this versus alternatives like get_spot_price, get_intraday_candles, or get_price_series. It's clear enough for a quote-focused need but lacks explicit exclusions.

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