debank_get_token_info

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

No annotations provided, so description carries full burden. It discloses that this is a read-only retrieval with historical price capability, but lacks information on rate limits, authentication, or error handling. The description is adequate but not highly transparent.

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 well-structured with a clear opening sentence, parameter list, return format, and examples. It is front-loaded but slightly verbose with extended examples; could be more concise without losing clarity.

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 the presence of an output schema (not shown but declared) and the detailed parameter/return descriptions, the tool is well-documented. However, it lacks error handling details and edge cases (e.g., invalid chain_id), which would improve completeness.

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 0%, but the description thoroughly explains each parameter (chain_id required, token_id vs token_ids, date format) and gives examples. This compensates effectively for the missing schema descriptions.

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 'Get token information and prices from DeBank' with specific verb and resource. It distinguishes itself from sibling tools like debank_get_user_tokens (user-specific) and debank_get_pool_info_tool (pool-specific).

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 clear context for each parameter (chain_id, token_id, token_ids, date) and includes multiple examples. It does not explicitly exclude alternative tools or states when not to use, but the examples effectively illustrate typical use cases.

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