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

Beyond the readOnly/openWorld annotations, the description discloses meaningful behavioral context: the data is creator-supplied, unverified by Arena, and excluded from incubation and ranking. That trust/provenance caveat is exactly the kind of context structured fields cannot carry. It does not discuss freshness or what happens if no history exists, keeping it short of a 5.

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?

A single tight sentence with no filler, and the key trust qualifier is front-loaded after the resource. It is perhaps too terse, but nothing is wasted.

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?

An output schema exists, so return shape needn't be explained, and the provenance caveats are well covered. The remaining gap is parameter meaning: with 0% schema coverage on strategy_id, the description should have said what identifier to pass, which it does not.

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% and the sole parameter strategy_id has no description in either the schema or the tool description. The description never explains that the prior history is keyed by a strategy identifier, so the agent must guess the parameter's meaning from the name alone.

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 names the resource (prior account history linked by the creator) but omits an explicit verb such as 'retrieve' or 'return', leaving the action to be inferred from the tool name. It does not distinguish itself from siblings like get_strategy or get_performance, though the caveats hint at its niche.

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?

It conveys implied usage guidance by stating the data is 'display only' and 'excluded from incubation and ranking', which tells an agent not to rely on it for scoring decisions. However, it never says when to call this instead of get_strategy or get_performance, nor does it name an alternative.

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