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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely non-obvious behavioral context beyond that: the data is ~15-minute delayed, which affects how an agent should present or trust the quotes. It does not discuss rate limits or refresh cadence further, keeping it just short of a 5.

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?

Two compact lines with zero filler: the covered instruments come first, then the quoted fields, then the latency caveat. Every clause carries information an agent needs.

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 zero-parameter read tool with rich annotations and no output schema, listing the returned fields plus the delay caveat covers nearly everything an agent needs to call and interpret it. The one gap is the absence of any routing hint against get_tokenized_stocks, which is the closest sibling.

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?

The tool takes no parameters, so the baseline is 4 and there is no parameter meaning to add or omit. The description instead spends its words on the return fields, which is the useful place to spend them here.

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 names a specific resource set (crypto-related equities like COIN, MSTR, miners, plus spot BTC/ETH ETF quotes) and enumerates the data returned (price, day change %, range, volume). It is clear what the tool fetches, but it never distinguishes itself from the sibling get_tokenized_stocks, which an agent could easily confuse with this one.

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?

Usage is only implied by the content scope: an agent can infer it should call this for traditional-market proxies on crypto. There is no explicit when-to-use, no exclusion of get_tokenized_stocks or list_markets, and no prerequisites stated, so selection between siblings still requires inference.

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