getBizTokenList

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

No annotations provided, so description carries full burden. It discloses return fields, mentions risk flag warning, and implies read-only nature. Could add more detail on behavior (e.g., no side effects), but sufficient.

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?

Concise, well-structured with clear sentences and bullet-like guidance. No wasted 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?

For a query tool with one optional parameter, the description covers return fields and usage guidelines. Lacks details on pagination or error handling, but overall complete enough.

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 0% schema coverage, description explains tokenTag parameter's purpose (filter by category) and notes it's optional. However, enum values are not described in detail, but context is adequate.

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 clearly states the tool's purpose: query on-chain tokens available for trading, optionally filtered by tag. It returns specific fields like DEX token code, contract address, risk flag, etc., and distinguishes from siblings like getBizTokenPriceList and getAssetList.

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?

Explicitly states when to use (user wants to discover tokens or expresses buy intent without specifying a token) and when not to use (for prices or holdings), with alternative tool names provided. Also includes an agent hint.

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