list_symbols

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

With no annotations, the description carries the behavioral burden, and it does a good job: it discloses the exchange-faithful spelling, BASE_QUOTE format, market_type domain, and case-insensitive substring filtering. It does not mention pagination, result ordering, or response shape, but the core behavior is clearly communicated for a simple list operation.

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?

The description is compact and every sentence adds useful information: what is listed, the exact naming format, the valid market_type values, the search behavior, and the intended usage. Nothing is wasted, and the core purpose is front-loaded.

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?

Given two optional parameters and no output schema, this description provides enough selective an agent to call the tool correctly: symbol format, filter semantics, and market type are all clear. It still doesn't describe the exact return structure, pagination, or what happens when no symbols match, so it is near-complete but not fully complete.

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 make up for the missing parameter docs. It does: it defines market_type as 'SPOT' or 'PERP' and describes search as an optional, case-insensitive substring filter. It leaves the default values to the schema, which is reasonable because the defaults are already visible there.

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 states a specific verb and resource: 'List real trading symbols on Pionex,' and further pins down the exact symbol format as 'BASE_QUOTE, e.g. BTC_USDT.' This makes it distinct from symbol-related sibling tools and clearly communicates what it returns.

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?

The description clearly tells an agent when to use this tool: 'Use this instead of guessing symbol names,' and it gives the market_type and search context. It also says exactly how the filter works, but it does not explicitly contrast against sibling tools like get_symbol_info or list_dual_symbols, so it stops short of a full when-not guide.

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