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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing: no read-only confirmation, data freshness, rate limits, or ordering behavior. It only hints at the trust proxy composition (activity, net flows), which is minimal.

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, but the mixed-language phrasing undermines clarity, so its brevity reflects under-specification rather than disciplined conciseness.

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 values needn't be explained, but for a ranking/overview tool with an undocumented parameter and no annotations, the description leaves too much unspecified about what the overview actually returns and how to invoke it.

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% for the single parameter top_n. The description only repeats 'Top N default 20,' which is already in the schema, and adds no meaning about what the ranking is by or how the cutoff affects results.

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 conveys the topic (Bittensor subnets ranked by emissions plus a trust proxy built from activity and net flows), which loosely distinguishes it from siblings like get_bittensor_subnet_trust or get_bittensor_network_health. However, it lacks a clear verb and is written in a garbled Czech/English mix ('subnety dle emisí'), making the exact operation ambiguous.

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 indication of when to use this tool versus the many related siblings (get_bittensor_subnet_trust, get_bittensor_network_health, get_trust_forensics). No prerequisites, exclusions, or alternative-routing guidance are given.

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