get_trade_history

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

The description indicates it returns sorted trades with pagination, but does not disclose that it is read-only (no side effects) or any other behavioral traits. Given no annotations, it carries the burden but omits explicit safety disclosure.

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 two sentences, no wasted words, and front-loads the core action.

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 the simple tool (list with pagination) and no output schema, the description covers purpose, sorting, and pagination. It could mention the default limit explicitly but is otherwise 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 100%, so the description adds no extra meaning beyond what the schema provides (limit, offset, defaults). The phrase 'optional pagination' is already implied by the schema.

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 'Retrieve closed trade history', specifying the verb and resource. It distinguishes from sibling tools like 'get_open_trades' (open trades) and 'get_trade' (single trade) by focusing on closed trades.

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 mentions optional pagination and sorting by ID, implying usage for retrieving multiple closed trades. However, it does not explicitly state when to use this tool over alternatives like 'get_open_trades' or 'get_trade'.

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