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

There are no annotations, so the description carries the behavioral burden. It communicates that the tool returns a set of tracking metrics (hit rate, P/L, open bags, round-trips), implying a read-only analytics lookup. However, it does not disclose response structure, error behavior, or whether results are snapshots or historical, leaving meaningful gaps.

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 the core result set front-loaded and the input requirement immediately after. There is no filler, redundancy, or unnecessary detail.

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 low-complexity two-parameter lookup, the description provides enough to attempt a call, but with no output schema, no annotations, and no differentiation from the many talon_* siblings, an agent may still be unsure about expected response format and when to prefer this tool. It is adequate but not complete.

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 only 50%: the handle property is described, while window only has an enum and default. The description mostly restates the handle constraint ('fomo.family handle or 0x wallet') and is completely silent on the window parameter, so it adds little semantic value beyond the schema.

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 clearly identifies this as a per-trader stats lookup ('One FOMO trader') and enumerates the returned metrics (hit rate, closed P/L, open bags, recent round-trips), so an agent can tell it apart from broader or list-oriented tools. It lacks an explicit verb like 'get/fetch' and doesn't reference sibling tools, so it stops short of a 5.

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?

The description provides input guidance ('Pass a fomo.family handle or a 0x wallet') but no conditions for when to choose this over siblings such as talon_traders, talon_wallet, or talon_closed. It does not mention alternatives, exclusions, or context that would guide tool selection.

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