trans_history

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

The description discloses the auth requirement, which is a behavioral trait, but does not mention other characteristics like rate limits, side effects, or return behavior. With no annotations, additional details 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 a single sentence, front-loading the auth requirement, and contains no redundant 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?

Without an output schema, the description should explain what the response contains or any constraints. It only states the purpose, leaving out details on data format, pagination, or time range that would help an AI agent.

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?

There are zero parameters, so the description is not required to add parameter information. The baseline score of 4 applies as no additional details are needed.

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 specifies the action 'Get' and the resource 'deposit and withdrawal transaction history', distinguishing it from sibling tools like trade_history or order_history.

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 includes a prerequisite '[REQUIRES AUTH]' but offers no explicit guidance on when to use this tool versus alternatives such as trade_history or order_history.

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