interTransferListQuery

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

With no annotations, description reveals the default time range (last 30 days) which adds some behavioral context. However, it does not disclose other traits like idempotency, rate limits, or any side effects.

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?

Two short sentences with no redundancy. Every part adds value: the purpose statement and the time range rule.

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 no annotations, the description is insufficient. It omits pagination behavior, parameter meanings, and response structure, leaving the agent to guess.

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% and description only hints at time parameters (startTime, endTime) implicitly. The other 5 parameters (transferId, coin, status, limit, cursor) are completely undocumented in the description, leaving the agent without guidance.

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 clearly states it queries internal transfer records between account types under same UID. It is specific but does not explicitly differentiate from sibling tools like universalTransferListQuery or transferCoinListQuery, which could overlap.

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?

No explicit guidance on when to use this tool versus alternatives. Only provides a default time range rule, but no context on prerequisites, exclusions, or recommended use cases.

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