getSpreadRecentTrades

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

With no annotations, the description carries full burden. It discloses key behavioral traits: returns up to 1000 records sorted reverse chronological, no authentication required. Missing details like rate limits or error handling, but for a public read endpoint this is sufficient.

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?

Description is well-organized with clear sections: main action, bulleted use cases, negative directives, notes, and agent hint. Every sentence adds value, no redundancy.

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?

Covers purpose, parameters, return fields, constraints, and alternatives. Lacks output schema but describes return fields. For a simple query tool, it is nearly complete; could mention pagination or error handling.

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 0%, so description must compensate. It explains the symbol parameter (required, source from getSpreadInstrumentsInfo) and implies limit usage via 'Returns up to 1000 records'. However, it does not explicitly describe the limit parameter's role, default, or range beyond the schema itself.

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?

Description starts with a specific verb ('Query') and resource ('recent public spread trading history'), and includes concrete return fields (price, quantity, taker direction, timestamp, cross sequence number). It explicitly distinguishes from sibling tools by naming getSpreadTickers and getSpreadOrderbook.

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?

Provides explicit use cases ('inspect recent trade flow', 'retrieve trade records for display', 'correlate trades with seq') and clear negative directives ('Do not use for best bid/ask or 24h stats — use getSpreadTickers instead'; 'Do not use for order book depth — use getSpreadOrderbook instead').

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