queryDepositRecords

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 important behaviors: API key support, time range rule, timestamp granularity, parameter priority, and txID date restriction. Missing details like pagination behavior and rate limits, but overall strong transparency.

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 extremely concise, using 5 bullet points to convey key information. No fluff, each sentence adds value. The opening line is direct, and the bulleted format is easy to scan.

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 annotations, and no output schema, the description covers critical aspects (time constraints, priority, txID restriction) but omits pagination (cursor), coin filtering, limit meaning, and response structure. Adequate for basic use but not fully comprehensive.

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%, so description must explain parameters. It explains startTime, endTime (millisecond, second-level, 30-day max, defaults), id (highest priority), and txID (Jan 1, 2024 onward). However, coin, limit, and cursor are not described, leaving gaps. Partial but helpful.

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 'Query on-chain deposit records', identifying the resource and action. It distinguishes from many sibling query tools by specifying 'on-chain' and providing detailed behavioral constraints, though it does not explicitly contrast with similar tools like queryInternalDepositRecords.

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 usage guidance: supports main/sub UID API keys, time range constraint (30 days), default behavior, parameter priority, and txID limitation. It does not specify when not to use or mention alternative tools, but the context is clear.

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