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

The readOnlyHint=true annotation already establishes that this is a safe, non-mutating read. The description adds that the list is provider-scoped and symbol-only, but says nothing about whether the set is static or refreshed, how large it is, or whether it is paginated — modest added value on top of 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?

A single front-loaded sentence with no filler, and the scope qualifier ("from the market-data provider") is placed where it matters. It is arguably too terse for a tool that seeds every other market call, but nothing in it is wasted.

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 an output schema present, the return shape need not be described, and a zero-parameter enumeration tool has little behavioral surface to cover. What remains missing is minor: whether the symbol list is stable across sessions and whether it should be treated as the canonical input vocabulary for the sibling market tools.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing filtering options that the empty schema does not support.

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 gives a specific verb ("Lists") and a specific resource ("coin symbols"), scoped to those "available from the market-data provider." That is enough to distinguish it from siblings like market_coin_details or market_candles, which operate on a specific coin rather than enumerating the valid universe, though it never names an alternative explicitly.

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: an agent can infer this is the discovery step for resolving valid symbols before calling quote or candle tools. There is no explicit statement of when to use it, no exclusions, and no named alternative, so guidance must be reconstructed from the purpose line.

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