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

With no annotations, the description carries the full burden, and it does add real context: the underlying data source (HL top-20 traders), the normalization range (0-100), and the per-call price ($0.007). However, it omits whether the tool is a read-only analytical query, how coins are scoped given zero input parameters despite the 'per coin' phrasing, and whether results cover all coins or a single one at a time.

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?

Pricing and purpose are front-loaded in a single tight sentence, followed by two short interpretive lines that earn their place by explaining the 0-100 scale. No filler or repetition.

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?

There is no output schema, so the description must convey the return shape; it gives the 0-100 scale and interpretation but not the granularity (one value per coin? a ranked list?), refresh cadence, or the universe of coins covered. For a zero-parameter analytical tool that ambiguity is the main remaining gap.

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?

The tool takes no parameters, so there is no schema semantics to supplement; the baseline applies. The description correctly avoids inventing parameters and instead spends its space on what the score means.

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 a specific verb and resource: 'Measure directional conviction of HL top-20 traders per coin', and even exposes the composition formula (position size x leverage x hold time, normalized 0-100). That is far more specific than a sibling like agent_stress_index or crowded_trade_detector, though it never explicitly contrasts itself against those alternatives.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. The 'High conviction = ... / Low conviction = ...' lines imply the analysis context in which the score is meaningful, but the agent must infer the decision rules itself.

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