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

Annotations already carry readOnlyHint and openWorldHint, so no safety disclosure is needed, and the description does not contradict them. It adds output context (risk tier definitions and the feed-symbol vs live-price distinction) but does not disclose behaviors like how limit affects results, data freshness, or rate limits.

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?

Three short sentences front-load the core action and resource, use examples to disambiguate symbols, and end with the routing note. Every sentence earns its place and there is no boilerplate.

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, the description covers what is returned (feed symbols with risk tiers), the optional filter, and the most relevant sibling alternative. It is less explicit about the limit parameter's behavior, but that is a minor gap for a simple read-only list.

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 parameter meaning. It clarifies the risk filter and explains the enum values (low/medium/high/new = volatility + liquidity), but limit is never described beyond its name/default in the schema, leaving a partial compensation gap.

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 an explicit verb ('List'), a specific resource (FTSO block-latency price feeds), and the returned attribute (Flare's published risk tier). The examples and final sentence distinguish this from get_flare_prices, so an agent can separate it from siblings.

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?

Tells the agent these are the symbols the on-chain oracle prices and explicitly directs live FLR/SGB/XRP values to get_flare_prices. This gives a clear when-to-use/alternative signal without requiring schema inspection.

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