price

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

No annotations are provided, so the description must cover behavioral traits. It states the tool fetches a spot price, implying a read-only operation. However, it does not mention data freshness, rate limits, or any side effects. The nature is benign, but transparency is minimal.

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 two sentences, but the first sentence is repeated verbatim, which is redundant. The example is helpful. Could be more concise without the repetition.

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 no output schema, the description provides an example URL but no return format. For a simple price tool, the description is mostly complete. Sibling tools are not referenced, but the purpose is clear enough for an agent to choose correctly.

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% (both parameters have descriptions). The description adds context about data sources (Coinbase, Alpaca SIP) which elaborates on the 'class' parameter. It does not add substantial meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly identifies the tool as providing current spot price for crypto (Coinbase) or US equities/ETFs (Alpaca SIP). The verb 'get' is implied, and the resource is specified as price data. The description distinguishes it from siblings like ohlcv or orderbook by focusing on spot price.

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 indicates when to use: for a current spot price of a given symbol. It gives an example query. However, it doesn't explicitly state when not to use or compare to alternatives like ohlcv or basis, but the context of siblings makes the purpose clear enough.

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