price

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the data routing layer and source venues (Coinbase, Alpaca SIP), which is genuinely useful context, but says nothing about authentication requirements, rate limits, quote freshness/delay, or behavior for unknown symbols.

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 body is duplicated verbatim ('Current spot price for crypto ... shared routing layer' appears twice), wasting roughly half the text. The remaining content is front-loaded and useful, but the repetition is a clear structural defect.

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?

With no output schema and no annotations, the description should ideally indicate the return shape (price, timestamp, currency) and error behavior for invalid symbols. It is adequate for a two-parameter quote tool but leaves the agent guessing at the response format.

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 description coverage is 100%, so both parameters are already documented (class = stock|crypto, symbol examples). The description's example URL adds the call shape but does not explain the class parameter's role or the curated-list fallback beyond what the schema states, so the 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?

States a specific verb+resource ('Current spot price for crypto ... or US equities/ETFs') and names the underlying venues (Coinbase, Alpaca SIP), which tells an agent this is a quote lookup rather than a candle/history call. It does not explicitly name the sibling it competes with (e.g. ohlcv, market_overview), so differentiation is inferential rather than stated.

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?

No guidance on when to use this versus alternatives such as ohlcv, market_overview, or orderbook. The example URL implies a simple lookup use case, but there is no stated condition, prerequisite, or exclusion anywhere in the description.

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