querySubMemberDepositRecords

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

It discloses the parent-child validation and time range limit, but does not cover pagination behavior, rate limits, or that the operation is read-only. With no annotations, more detail would be beneficial.

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, uses bullet points for clarity, and front-loads the main purpose. It could be slightly more structured but is well-organized.

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?

No output schema is provided, and the description does not explain what the response contains (e.g., fields, pagination details). For a query tool, this is a notable omission.

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?

Only subMemberId and time range parameters are explained via constraints; six other parameters (id, txID, coin, limit, cursor) are undocumented. With 0% schema coverage, the description leaves significant gaps.

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 on-chain deposit records for a sub-account using the main UID API key, distinguishing it from sibling tools like queryDepositRecords (for main account) and 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 constraints (time range, required subMemberId) and a validation check, but does not explicitly state when to use this tool versus alternatives or when not to use it.

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