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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact, the 5 qps rate limit, but says nothing about pagination behavior or response shape despite paging parameters being available.

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 short lines with the core action front-loaded and the rate limit immediately after, with no filler. It is efficient, though arguably under-specified rather than genuinely well-structured.

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 read-only lookup with full param coverage and no output schema, the description is minimally adequate: the action, rate limit, and filterable params come from structured fields. It omits what 'details' actually contains and how it differs from sibling symbol tools, which an agent would need to choose correctly.

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 the schema fully documents page, page_size, symbols, and exchange (including the enum meanings), making 3 the baseline. The description adds no syntax, format, or cross-parameter guidance (e.g., how symbols and exchange interact) beyond what the schema already provides.

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+resource ('Query symbol details'), but 'details' is vague about what is actually returned, and it does nothing to distinguish itself from the sibling cex_stock_query_stock_symbols or the various spot/currency lookups. An agent knows it queries something symbol-related, but not how this differs from the plain symbol list.

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?

No guidance on when to use this versus cex_stock_query_stock_symbols or cex_stock_query_stock_exchanges, and no prerequisites or exclusions are given. The agent is left to infer usage entirely from the name.

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