get_recent_trades

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

No annotations exist, so the description must fully disclose behavior. It omits key traits: whether the operation is read-only, authentication needs, rate limits, data freshness, or side effects. Only basic parameter descriptions are provided.

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?

Two sentences, no redundancy. The first sentence states the purpose; the second details args. Every word is necessary.

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?

An output schema exists, so return value details are not required. However, the description does not specify limits on the number of trades returned, pagination, or default date range. It covers basic usage but leaves ambiguity about result scope.

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 description explains both parameters ('Market pair (e.g., 'BTC_USDT')' and 'Type of trades to retrieve ('buy' or 'sell')') with examples and allowed values. This adds value over the schema, which has zero percent description coverage at the top level.

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 'Get recent trades for a specific market,' specifying the verb (Get) and resource (recent trades) with a market qualifier. While distinctive from siblings like get_market_activity, it does not explicitly contrast with alternatives.

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 versus siblings like get_market_activity or get_orderbook. Lacks context for appropriate invocation or exclusion criteria.

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