universalTransferListQuery

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

Annotations already declare readOnlyHint and openWorldHint, and the description aligns with read-only behavior. It adds meaningful behavioral context beyond annotations: API-key-based visibility restriction and the 30-day default window. This is valuable transparency, though it does not cover pagination or status-filter behavior.

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 concise and efficiently formatted with bullets, front-loading the main purpose and then clarifying access rules. It does not waste words, though it could add more parameter detail without becoming bloated.

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?

With 7 parameters, no output schema, and a large sibling list, the description is incomplete for reliable tool invocation. It provides valuable context for API key access and time defaults, but omits essential filter parameter semantics and does not clarify how this differs from related transfer queries.

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%, so the description must compensate for the 7 undocumented parameters. It only hints at time-related behavior with the 30-day default rule and does not explain coin, limit, cursor, status, or transferId. This leaves most parameter semantics to be inferred.

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 operation ('Query universal transfer records') and the resource, and the API key scope bullets add useful specificity. However, it does not explicitly distinguish this from the similarly named sibling interTransferListQuery, so it falls short of a 5.

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 usage context by explaining what master and sub account API keys can query, and it documents the default time range when no time parameters are supplied. It does not name alternative tools or exclusion conditions, so it lacks the explicit when-not-to-use guidance needed for a 5.

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