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. It mentions what data is returned (rank, incentive, stake, roles, endpoints) but doesn't state whether it's read-only, if there are rate limits, authentication requirements, or how the trust ranking is computed or sorted.

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?

A single sentence that is front-loaded and efficient, though the use of non-English term 'řazení' (sorting/ranking) may cause confusion for an English-speaking agent.

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?

Given the complexity of a subnet trust tool with no annotations, no schema descriptions, and an output schema that exists but isn't referenced, the description is incomplete. It doesn't explain the output structure, parameter meanings, or operational context.

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?

With schema description coverage at 0%, the description should compensate but doesn't explain the netuid or limit parameters. Baseline for 2 parameters is 4, but the lack of param details in the description reduces this to 3 as it adds only marginal value beyond the schema's type information.

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 it returns neuron trust ranking in a subnet (rank × incentive × stake, validator/miner, endpoint), naming a specific resource. However, it's written in partially non-English text (řazení) and doesn't explicitly differentiate from sibling tools like get_bittensor_trust_overview or get_bittensor_network_health.

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?

No guidance on when to use this tool versus alternatives such as get_bittensor_trust_overview or get_bittensor_network_health. The agent must infer usage context from the name and description alone.

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