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

Annotations already declare the safe read profile (readOnlyHint=true, openWorldHint=false), yet the description adds real operational context: the perp default, Binance's lot-size ticker prefixing (1000PEPEUSDT vs PEPEUSDT on spot), and spot-only coins/quote assets. It omits return shape and pagination/limit behavior, which keeps it from 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 dense sentences, front-loaded with the core action before the ticker caveat. Every clause carries information, though the second sentence is long and would read better as a short list of spot-only quirks.

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 should ideally sketch what comes back (list of symbols/tickers). It conveys scope, defaults, and ticker conventions well enough for correct invocation, leaving only the return shape implicit.

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 67% (limit is undocumented in the schema). The description compensates meaningfully for the two semantic parameters: it confirms perp as the default market and warns that query strings may need the exchange's prefixed form, which the schema's simple "PEPE" example does not convey.

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 a specific verb (search) and resource (every market with history in the archive), and explicitly splits the corpus into USD-M perpetual futures (default) and spot. No sibling tool covers symbol lookup, so the scope is unambiguous for an agent.

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?

"Worth calling before writing a strategy" gives a clear when-to-use trigger and explains the failure mode of skipping it (guessing the ticker finds nothing). It stops short of explicit exclusions or naming an alternative, but no sibling alternative exists.

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