get_my_trade_history

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

In the absence of annotations, the description must disclose behavioral traits. It mentions returns (outcomes, PnL, AI reasoning) but does not clarify if it is read-only, pagination behavior, error conditions, or rate limits. The safety profile is unclear.

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?

A single, concise sentence that front-loads the purpose. However, it lacks detail that could be added without verbosity. Still efficient.

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?

With no output schema and minimal description, the agent lacks information on return format, pagination, or handling of empty trades. For a tool with two optional parameters and no annotations, the description is insufficient for complete understanding.

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 description coverage is 0%, and the description adds no information about the two parameters (limit and symbol). The agent cannot infer what these parameters do from the description alone.

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 retrieves past trades with outcomes, PnL, and AI reasoning. Verb 'Get' and resource 'your bot's past trades' are specific, and it distinguishes itself from siblings like get_my_positions or get_my_portfolio.

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 vs alternatives like get_my_positions or get_market_data. No context on prerequisites, filtering, or typical use cases is provided.

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