queryCoinChainInfo

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

Despite no annotations, the description goes beyond basic functionality by explaining key behavioral details: the effect of omitting the coin parameter, the meaning of status values ('0' = suspended, '1' = normal), interpretation of 'remainAmount', and the impact of compliance whitelist filtering. This provides useful context for the agent.

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?

Five well-structured sentences with bullet points that front-load the main purpose. Every sentence adds value, no redundancy. Efficient and clear.

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 no output schema, the description adequately describes the return structure: all coins if no coin specified, each coin includes chain list with deposit/withdraw status, max withdrawal amount, and compliance filtering. This covers the key elements needed to understand the tool's results.

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 0%, but the description compensates by explaining the semantics of the sole parameter 'coin': when omitted, all coins are returned. This adds meaning beyond the schema's bare type definition.

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?

Description states a clear verb+resource: 'Query coin information' and specifies scope including chain configuration, deposit/withdraw status. It distinguishes itself by detailing that omitting the optional 'coin' parameter returns all supported coins, which differentiates it from possibly more specific coin queries among 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?

Description implies usage for querying coin details but does not explicitly state when to use this tool versus alternatives like 'queryCoinList' or other query tools in the sibling list. No 'when not to use' or alternative recommendations are provided.

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