queryFundingDetailApi

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

Since no annotations are provided, the description carries full behavioral burden. It describes default behavior (last 7 days), constraints (time interval), and pagination. It implies a read operation without side effects. Lacks explicit mention of idempotency or rate limits, but still good.

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 (4 short sentences) and well-structured with bullet points. Every sentence adds value, and it is front-loaded with the purpose. No wasted words.

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 no output schema, the description explains pagination (nextPageCursor) which hints at response structure. It covers all needed usage constraints. It could mention what fields are returned, but for a query tool this is sufficient.

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 compensate. It adds meaning for 3 of 4 parameters: createTimeFrom, createTimeTo, and cursor. The 'limit' parameter is not described. Overall adds significant value beyond schema.

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 transaction records of the funding account. It provides specific resource (funding account) and action (query records), distinguishing it from other query tools like queryBalance or queryTrade. However, it does not explicitly differentiate from siblings, so a 4 is appropriate.

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 gives explicit usage context: time parameters must be used together and interval cannot exceed 7 days, with default to last 7 days. It also mentions cursor-based pagination. However, it does not specify when not to use this tool or alternatives, so 4.

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