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

With no annotations, the description carries the full burden of behavioral disclosure, and it says nothing about whether this is a read-only fetch, how fresh the snapshot is, whether it is computed on demand, or any auth/rate constraints. It spends its words enumerating output fields rather than behavior beyond them.

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?

It is short and front-loaded with no filler sentences, but the content is a comma-separated field list that reads as under-specified rather than economical. The one interpretive sentence about high flow is the only element that genuinely earns its place.

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 the description needn't document return values, which excuses the field enumeration. However, for a single-required-parameter tool with zero annotation coverage, it leaves the input semantics and usage context entirely unaddressed, so it is only adequate rather than 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 coverage is 0% for the single parameter (netuid: integer, title 'Netuid'), and the description never mentions or explains it – not even that it identifies a subnet. The description therefore does not compensate for the documentation gap left by 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 reads as an output-field manifest (flow_score, whale_signal, whale_ratio, composite, dev, eval) rather than a verb+resource statement of what the tool does; 'snapshot' implies retrieval of momentum metrics for a subnet, but no explicit action is stated. It never distinguishes this from siblings like subnet_detail or screener_top, which likely expose overlapping subnet metrics.

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 only usage-adjacent content is the interpretive rule 'High flow = strong momentum,' which explains how to read the score, not when to call the tool. There is no mention of alternatives, prerequisites, or situations where another tool is preferable.

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