getRwaOrderList

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

No annotations provided, so description carries full burden. It discloses rate limit (10 req/s), behavior that exact identifiers override other filters, default time ranges, and a 180-day lookback limit. This provides sufficient behavioral insight for safe usage.

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 with clear sections: purpose statement, rate limit, and notes. Each sentence provides essential information without redundancy. It is well-structured and front-loaded with the core purpose.

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 no output schema, so description cannot explain return values. However, it covers behavioral aspects, rate limits, defaults, and edge cases (exact lookup behavior, lookback limit). For a query tool, this is largely complete. Minor missing: pagination cursor behavior is not explained.

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 mentions key parameters (orderId, orderLinkId, orderType, productId, startTime, endTime, limit) and explains their behavior (exact vs paginated, filter overriding, defaults). It adds meaning beyond the bare schema, though not every parameter is detailed.

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 'Query RWA order history' with specific verb 'Query' and resource 'RWA order history'. It distinguishes from sibling tools by focusing on RWA orders, which are separate from general order history tools like getOrderList.

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 explains when to use exact lookup (when orderId or orderLinkId provided) vs paginated listing, and provides default time ranges and lookback limit. It does not explicitly list when NOT to use, but the sibling list contains many order-related tools, and the RWA specificity is clear.

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