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

readOnlyHint=true already declares the tool safe, and the description adds meaningful context: it pulls from two distinct sources (Robinhood bid/ask versus Chainlink on-chain). However, it does not disclose behavior for unknown symbols or data freshness, leaving some behavioral gaps beyond the annotation.

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 a single 14-word sentence, front-loaded with the two price sources and scoped by 'for one ticker'. Every word earns its place; there is no fluff or redundancy.

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, read-only price tool, the description covers what data is returned (Robinhood bid/ask and Chainlink on-chain price) and what identifies it (ticker). It does not detail output structure or error handling, but with no output schema and a simple read operation, the gaps are minor.

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 0%, so the description must carry the meaning of 'symbol'. The phrase 'for one ticker' directly equates the parameter to a ticker, adequately conveying semantics for this single string param, though the expected format (e.g., 'AAPL' vs 'aapl') is not stated.

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 specifies the resource (price for one ticker) and the two data sources (Robinhood bid/ask, Chainlink on-chain), making it clear what the tool reports. It lacks an explicit verb like 'get' or 'fetch', and does not explicitly differentiate from the sibling metamuse_quote, so it loses a point.

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?

There is no guidance on when to use this tool versus alternatives. Given the sibling metamuse_quote likely overlaps in price data, the absence of any distinction or when-to-use note leaves the agent to guess which tool fits.

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