get_trade_history

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

Without annotations, the description must disclose behavioral traits. It only states it returns 'recent trades,' but omits whether it is read-only, authentication needs, rate limits, or output format. The description adds minimal behavioral context beyond the function name.

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 a single sentence, too brief to be informative. While concise, it sacrifices critical details that an agent needs, such as parameter explanations and output structure.

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 annotations, no output schema, and only three parameters (one required), the description fails to provide sufficient context for correct usage. It does not describe the return format, pagination, or any constraints, leaving the agent underinformed.

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 does not explain any of the three parameters (token, type, limit). The agent must rely solely on the schema, which lacks descriptions. No value is added for parameter understanding.

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 'Recent trades for a token' clearly indicates the tool retrieves trade data for a specific token. It distinguishes from sibling tools like get_orders or get_price_history, but lacks specificity on what constitutes 'recent' and does not differentiate from similar trade-related tools like preview_trade.

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 is provided on when to use this tool versus alternatives such as preview_trade, get_order_history, or other trade-related functions. The description offers no context for appropriate invocation scenarios.

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