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

No annotations provided, so description carries full burden. Mentions it returns a list of symbols but does not disclose pagination, sorting, or whether the output is truncated. Could be more transparent about the behavior with filters or large result sets.

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 sentences, front-loaded with purpose and usage. Every sentence adds value with no unnecessary words.

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 4 optional parameters, no output schema, and moderate complexity (filtering, pagination), the description lacks important details such as return format, how filters interact, and pagination semantics. Does not fully cover the tool's capabilities for an agent.

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?

With 4 optional parameters and 0% schema description coverage, the description adds no meaning to any parameter. Does not hint at filtering by type, market, or pagination with limit/offset. This is a critical gap for a tool with optional filters.

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?

Clearly states the tool queries all tradable symbols on TickDB and specifies the asset count (37,527+). Explicitly frames it as a discovery/verification tool for symbol codes, distinguishing it from sibling data retrieval tools like get_kline or get_order_book.

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?

States 'Use this to discover and verify correct symbol codes before other calls,' providing explicit usage context and suggesting it is a prerequisite. Lacks when-not or alternatives, but the guidance is clear and actionable.

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