get_global_trades

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

No annotations are provided, so the description carries the full burden and does disclose the return payload (token names, amounts, prices, DEX names, timestamps), which is genuinely useful. It says nothing about pagination, result caps, rate limits, or whether the 'recent' window interacts with timezone, so the behavioral picture is incomplete for a zero-annotation tool.

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 tight sentences: the first defines the data source and scope, the second enumerates the return fields. No filler, and the essential scoping information is front-loaded.

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?

For a one-parameter read tool with full schema coverage and no output schema, the description adequately covers purpose and return contents. The notable gap is sibling disambiguation against get_historical_trades and get_token_trades, which the agent needs in order to select correctly.

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 100%: the single 'timeframe' parameter is fully documented in the schema with its allowed values and default. The description adds no timeframe syntax beyond the vague word 'recent', so the baseline of 3 applies.

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?

States a specific verb and resource ('Get recent global trade data') plus the scope ('across all Cardano DEXes'), and even enumerates the returned fields. It implicitly differentiates from siblings like get_historical_trades ('recent' vs historical) and get_token_trades ('global' vs token-specific), but it never names those tools, so the differentiation is left to inference.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternatives are named, despite three sibling tools (get_historical_trades, get_token_trades) that clearly overlap in intent. The word 'recent' implies a time-bounded read, but the agent must guess which trade tool to pick.

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