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

No annotations are provided, so the description must carry the load: it states the tool is FREE and enumerates returned fields, which is useful disclosure for a read-only catalog. It stops short of stating pagination behavior or whether any auth is required, which is the remaining gap.

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?

Front-loaded with 'FREE.' and compressed into two dense sentences with no filler. Density comes at some cost of readability (perp, xStocks, Ondo GM, trade.xyz assumptions), but every clause carries information.

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?

There is no output schema, so the description must describe returns, and it does: ticker, venue, identifier, type, live, tradable_now. The 2,000+ row warning lives only in the schema, so the description itself doesn't warn about response size or pagination.

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 100%, so the baseline is 3; the description earns extra by explaining that markets carry a symbol, Lighter market_id, Solana mint, or Ondo contract, which clarifies what identifier-shaped results map to. Minor risk: it mentions 'OKX perps' while the venue parameter enumerates hyperliquid-xyz, aster, lighter, xstocks-solana, ondo-gm, leaving ambiguity for an agent trying to filter by OKX.

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?

Specific verb + resource: a catalog of stock perps and tokenized stocks across named venues, with an explicit per-market field list. It also distinguishes itself from siblings by naming get_quote and get_funding as downstream consumers.

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?

'Use first to see where a ticker trades before get_quote or get_funding' gives an explicit ordering and names the alternatives. Combined with the schema's ticker recommendation, an agent knows exactly when to reach for this tool.

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