queryEscrowSubMembersV5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds rich behavioral detail: cursor-based pagination with nextCursor=0 as the terminal sentinel, default page size of 100, account type always 6, privacy-masked username, and the fact that these accounts cannot be accessed like normal sub-accounts. No contradiction with annotations exists.

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 well-structured with bolded sections and a front-loaded summary. However, it is somewhat repetitive: Private Wealth Management appears multiple times, and pagination details are covered in both the important notes and the dedicated pagination section, so it could be trimmed without losing essential information.

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 that there is no output schema, the description compensates by listing the response fields, pagination behavior, permissions, and use cases. Minor gaps remain, such as explicit parameter-name mapping and any rate-limit or error behavior, but for a read-only query tool the context is largely complete.

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?

The schema has 0% description coverage, but the description compensates by explaining page size defaults/maximum and the meaning of nextCursor, including that nextCursor=0 indicates the last page. It does not explicitly map these explanations to the exact parameter names in a single place, but it is sufficient for invocation.

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 opens with a specific verb and resource: 'Query escrow (fund management) sub-accounts in paginated format.' It clearly differentiates from sibling tools like querySubMembersV5 by emphasizing that only escrow sub-accounts are returned and that it is used for Private Wealth Management scenarios.

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?

It provides strong context: use the trading team API key, only escrow sub-accounts bound to the requesting trading team are returned, and typical use cases are listed. However, it does not explicitly name or contrast with the sibling querySubMembersV5 tool, so it stops short of full when-to-use versus alternative guidance.

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