queryTrade

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

No annotations provided, so description carries burden. It discloses returned information (status, exchange rate, amounts, timestamp, user ID) but does not explicitly state it is read-only or note any authorization requirements or rate limits. Adequate but not exhaustive.

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?

Well-structured with headers and bullet points, front-loading purpose. Every sentence adds value, no fluff. Concise yet informative.

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, description adequately covers returned fields. Covers query options and use cases. Could mention if there are rate limits or pagination, but for a simple query tool, it is fairly complete.

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%, but description adds meaning by distinguishing tradeNo (system-generated) from merchantRequestId (custom) and stating at least one is required. This goes beyond the schema which only provides names and types.

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 detailed information and status of a specified trade. It uses a specific verb (query) and resource (trade), and the context of sibling tools like getOrderDetail and queryTradeHistory helps differentiate it, though not explicitly.

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?

Provides explicit constraints (at least one query parameter required) and lists three specific use cases (poll for status, reconcile trades, display details). Does not explicitly state when not to use, but guidance is clear enough.

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