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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description's job is to add context. It does: results are capped at 50, matching requires every query word (AND semantics), ids have a specific format, and only one free preview symbol is available on binance-futures — a real behavioral/access constraint not expressed anywhere in the structured fields.

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?

Three short sentences, front-loaded with the core behavior and the result cap, then the id format, then the access caveat. No filler, though the id-format example is somewhat redundant with the preview-symbol sentence that follows it.

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, and the description compensates by showing the exact id shape a caller will receive, plus the result cap and the preview limitation. For a two-parameter lookup tool this is close to sufficient; the main gap is any statement of ordering or what happens when a query word matches nothing.

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 50%: query is documented in-schema, but exchange is a bare enum with no explanation. The description adds AND-matching semantics and the 50-result cap that the schema's 'Words to match' does not convey, but it leaves the exchange parameter entirely unexplained (which venue each enum value represents, whether coverage differs). Partial compensation only.

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 names a specific verb+resource: it returns symbol ids on one exchange matching every word of a query, capped at 50. That is concrete enough to distinguish it from generic siblings like search and fetch, though it never explicitly contrasts itself with those siblings.

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?

Usage is implied by the semantics of the query (find symbol ids before fetching data), and the free-preview note hints at an access tier restriction. However there is no explicit when-to-use or when-not-to-use guidance, and no mention of an alternative for cases where this tool is insufficient.

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