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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds ranking composition (emission, activity, net flows) and a default length, but the 'trust proxy' is left undefined, which is the key ambiguous behavior for interpreting results.

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?

One front-loaded sentence with the ranking basis first and the count behavior second; no wasted clauses. Slightly over-compressed in that the central term 'trust proxy' is never unpacked.

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?

A small tool (one optional param) with an output schema, so return shape needn't be described. The only real gap is the undefined trust proxy metric, which matters for interpreting comparisons.

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%, so the description must carry the load; it does by explaining that top_n bounds the returned ranking and that the default is 20. No further syntax exists for a single integer, so this is close to adequate.

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 states a specific verb and resource ('Bittensor subnets ranked by emission plus a trust proxy') and names the ranking inputs. It does not explicitly distinguish itself from close siblings like get_bittensor_subnet_trust or get_bittensor_network_health, so an agent must infer the boundary.

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?

'Use it to compare subnets' implies the usage context but gives no when-not conditions and names no alternative among the many trust/Bittensor siblings. The usage signal is present but thin.

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