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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context about the data boundary (user/organization scoped, excludes platform trades), but says nothing about ordering, default sort, or whether results are capped beyond the limit parameter.

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 short sentences with no filler, and the core scope is front-loaded ahead of the exclusion. Every clause carries information an agent would otherwise have to guess.

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 simple paginated read tool with full schema coverage and complete annotations, the definition covers scope and the key data boundary. Only minor details such as result ordering are absent, which an agent could discover from the response.

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%, so the schema already documents asset, limit, offset, outcome, and strategy_id, including defaults. The description adds no syntax or filtering nuance beyond implicitly confirming the user/organization scoping that makes no user parameter necessary, so baseline 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?

The description gives a specific verb and resource ("Read trade history recorded in MangroveAI") and adds the important negative scope "This does not read platform trades," which prevents an agent from confusing it with platform-wide trade readers. It does not, however, name or distinguish itself from near siblings such as get_trades_for_strategy or get_backtest_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?

Usage is implied through scope: the authenticated user/organization's own recorded trades, not platform trades. There is no explicit when-to-use statement and no named alternative for strategy-specific or backtest trade history, so the agent must infer routing from sibling names alone.

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