wallet_get_trade_history

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

No annotations and no description of side effects, read-only nature, data freshness, or pagination behavior. The cursor parameter implies pagination but is unexplained.

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 extremely short (6 words) but lacks essential information, making it under-specified rather than concise.

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?

With two parameters, no output schema, and many sibling wallet tools, the description is far from complete. It omits pagination details, output format, and any prerequisites.

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 0%. The description does not explain the two parameters (wallet format, cursor usage) beyond the schema itself, failing to compensate for the gap.

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 'Fetch wallet trade history via Dritan,' clearly indicating the action and resource. However, it does not differentiate from sibling tools like wallet_get_holdings or wallet_get_performance, and 'via Dritan' is vague.

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 alternatives such as wallet_get_performance or wallet_get_holdings. No prerequisites or context for the wallet parameter.

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