universalTransferListQuery

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

No annotations are provided, so the description carries full burden. It discloses key behavioral traits: differences in queryable records by API key type and default time range. However, it does not mention pagination, rate limits, or whether the operation is read-only. The description adds some value beyond the schema.

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 relatively concise (3 sentences plus bullet) and front-loads the main purpose. It uses bullet points for key distinctions. No wasted words, but could be slightly more compact.

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 7 parameters, no output schema, and no param descriptions, the description is incomplete. It does not cover pagination, filtering parameters, or response format. For a query tool, more context on result structure and use of cursor/limit is needed.

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 description coverage and 7 parameters, the description fails to explain most parameters. It only mentions time range behavior (startTime, endTime default) but ignores transferId, coin, status, limit, cursor. This requires the agent to infer from names, which is insufficient.

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 queries universal transfer records and explains the scope for master and sub API keys. The verb 'Query' and resource 'universal transfer records' are specific. It distinguishes itself from sibling tools like interTransferListQuery by its scope.

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 explicit guidance on when to use the tool with master vs sub API keys and includes time range rules. However, it does not mention alternative tools or when not to use it, though the context implies uniqueness.

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