getTokenOrderList

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

No annotations exist, so the description should fully disclose behavior. It only states it's a query and includes a rate limit. It does not mention pagination (cursor, limit), what constitutes 'order history' (completed vs pending), or behavior when multiple filters are applied.

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 (two sentences plus rate limit) and front-loaded with the main purpose. While it could include more detail, it avoids unnecessary 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?

The tool has 8 parameters and no output schema. The description omits context on return format, pagination, filtering by time/orderType, and cursor usage. It is not sufficiently complete for an agent to use confidently.

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 the description must compensate. It explains orderLinkId and orderId but ignores other parameters (coin, orderType, startTime, endTime, cursor, limit). The rate limit note adds some value but does not address parameter meaning.

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 it queries 'BYUSDT Token order history', using a specific verb and resource. It distinguishes from sibling tools like getOrderHistory (general) and getLPOrderList (liquidity pools) by specifying the token type.

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?

No guidance on when to use this tool versus alternatives such as getOrderHistory, getOrderList, or getLPOrderList. The description does not mention exclusions or preferred use cases.

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