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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the concrete rate limit of 5 qps, which is useful behavioral context not present in annotations, but does not discuss pagination, auth, or return behavior.

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 extremely terse and front-loads the purpose before the rate limit, with no filler sentences. However, the purpose sentence is so minimal that it borders on under-specification rather than ideal conciseness.

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?

For a simple read-only list tool with 100% schema coverage and annotations covering the safety profile, the description is minimally adequate. It still leaves gaps around when to use this tool versus siblings and does not describe the return shape, though no output schema exists to cover that.

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 all five parameters (page, symbols, exchange, page_size, with_desc_i18n) are already well documented in the schema. The description adds no parameter-level information beyond what is in the structured input schema, making the baseline 3 appropriate.

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 says 'Query symbol list', which identifies a verb and a resource but does not specify that these are stock symbols or what distinguishes this tool from siblings like cex_stock_query_stock_symbol_detail. It is vague and relies on the tool name for context.

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 provides no guidance on when to use this tool versus alternatives such as cex_stock_query_stock_exchanges or cex_cfd_query_symbols. The only extra information is a rate limit, which is not usage guidance.

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