queryInternalDepositRecords

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

With no annotations, the description carries behavioral burden. It discloses the 30-day window, status filter meanings, and API key accessibility. However, it does not mention pagination behavior (cursor), rate limits, idempotency, or what happens with invalid parameters.

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 with three bullet points, no wasted sentences, and important details front-loaded (platform scope, accessibility, time window).

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 0% schema coverage and no output schema, the description is incomplete. It covers some constraints but omits parameter details for 4 out of 7 parameters, return format, and error handling. The tool's complexity (7 parameters) demands more comprehensive explanation.

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 only explains the 'status' parameter values and the time window constraint for startTime/endTime. Other parameters (txID, coin, cursor, limit) are not described, leaving significant gaps for an agent.

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 deposit records within the Bybit platform, distinguishing it from on-chain deposit queries (e.g., queryDepositRecords). The verb 'Query' and resource 'deposit records' are specific, and the platform scope is explicitly highlighted.

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 useful constraints: accessible via Master/Sub Member API Key, max 30-day window, defaults to last 30 days. However, it lacks explicit when-to-use guidance compared to sibling tools like queryDepositRecords, and does not describe when not to use this tool.

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