kraken_get_recent_trades

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

No annotations are provided, so the description must bear the full burden. It only says 'Retrieve the most recent public trades', which hints at a read-only public endpoint but fails to disclose pagination behavior via the 'since' cursor, rate limits, or data ordering. The word 'public' implies no authentication but is not explicit.

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, concise sentence with no fluff, front-loading the action and resource. It is appropriately brief for a simple market data tool.

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?

The tool is a simple public data retrieval with only 2 parameters and an output schema, so it doesn't need to explain return values. However, the description is minimal, lacking context on pagination, usage alternatives, and authentication expectations, making it only partially 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?

Both parameters are fully described in the input schema (pair with example, since as pagination cursor). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate given the high schema coverage.

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 states 'Retrieve the most recent public trades for an asset pair' with a specific verb and resource, clearly distinguishing it from sibling tools like 'kraken_get_recent_spreads' (spreads) and 'kraken_get_trades_history' (private account 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 provides no guidance on when to use this tool versus alternatives. It does not mention 'use for market data' or 'for private trades use kraken_get_trades_history'.

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