get_trade_history

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

With no annotations, the description discloses return details (trade ID, order ID, quantity, price, time, settlement status) and implies a read-only operation via 'Fetch.' However, it lacks explicit mention of auth requirements or pagination behavior.

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 well-structured with a concise purpose sentence, parameter explanations, and return details. Every sentence adds value without unnecessary fluff.

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?

For a simple tool with an output schema, the description covers purpose, parameters, and returns sufficiently. It omits usage alternatives and auth context, but the tool's simplicity keeps it adequate.

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?

The schema provides no descriptions (0% coverage) beyond string types, but the description fully compensates by specifying 'YYYY-MM-DD' format and examples for both from_date and to_date.

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 'Fetch trade history within a date range,' identifying a specific verb, resource, and scope. It naturally distinguishes from sibling tools like get_all_orders (orders) and get_holdings_summary (holdings).

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 provides a clear context for use (trade history in a date range) but does not explicitly mention alternatives or when not to use this tool. Sibling tools exist but are not referenced.

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