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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real context beyond them: the data is public, results are ordered newest-first, and the exact entry categories returned are spelled out. It stops short of stating page size defaults or that the response carries a next_cursor, though the cursor param hints at it.

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, front-loaded with the resource and scope, then the pagination controls. No filler and nothing repeated.

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?

No output schema exists, so the description carries return-value burden; listing the activity types and ordering largely covers it. Minor gap is that it doesn't confirm the response is paginated with a next_cursor field, which an agent must infer from the cursor parameter.

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 100%, so all four parameters including allowed filter values and limit bounds are already documented in the schema. The description only echoes that `filter` narrows and `cursor` pages, adding no semantics beyond that. 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?

States a specific resource and scope: a public trader's ledger activity keyed by handle, with the returned entry types enumerated (swaps, deposits, withdrawals, transfers, fees) and ordering given as 'newest first'. That enumeration differentiates it from get_trader_portfolio and get_trader without naming them.

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?

'Narrow with `filter`, page with `cursor`' implies how to use the parameters but gives no when-to-use guidance and never mentions alternatives such as get_trader_portfolio for holdings or list_traders for discovery. An agent gets usage hints, not selection criteria.

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