Get symbols info

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

Annotations already cover readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is handled. The description does add one genuinely useful behavioral fact beyond the annotations: the rate-limit weight of 5. It says nothing about return fields, caching, or pagination, so this is adequate but thin.

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?

It is short and front-loaded, but the first line duplicates the tool title verbatim and earns nothing, and the 'Weight: 5' sentence is dropped in without explaining what weight governs.

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 is the only place to learn what 'symbol info' actually contains, and it omits that entirely (filters, precision, contract specs?). Given a simple two-parameter read tool with full annotation coverage, this is minimally viable but leaves a real gap about the response content.

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 100%, so both parameters (type enum and comma-concatenated symbols) are fully documented in the schema itself. The description adds no syntax, default, or filtering detail beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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 verb and resource ('Get trading pair information'), so the agent knows it retrieves market metadata. However, the first line just restates the title, and it offers no differentiation from siblings like pionex_market_get_tickers or pionex_market_get_depth, all of which return market data.

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?

There is no when-to-use guidance, no mention of alternatives, and no prerequisites. The only extra sentence, 'Weight: 5,' is a rate-limit cost, not usage direction.

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