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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes well beyond them by disclosing the API key requirement and the paid-call model: $0.005 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. The remaining gap is operational behavior such as rate limits or total result-set size, which keeps it just short of top marks.

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?

The description is front-loaded with the core definition plus ranking methodology, then the sibling routing and pricing. It is a dense run of sentences, but each one carries distinct information (scope, auth, alternatives, cost) with no filler.

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?

For a two-parameter read-only list tool with an output schema already describing the response shape, the definition covers everything needed: what is returned, how ranking works, the auth prerequisite, alternatives, and cost. An agent could invoke it correctly on the first try.

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 100%, with both page and limit documented and bounded (limit max 100, default 20), so the schema carries parameter meaning. The description adds nothing about pagination or the limit cap, so the baseline 3 for a fully documented schema is appropriate.

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?

It names a specific resource (top Bittensor validators), the ranking method (Taostats' global weighted stake = root stake plus alpha stake valued in TAO across all subnets), and the returned fields (subnet counts, dominance %, nominator counts, commission take). It also explicitly distinguishes itself from crypto_tao_subnet_validators and crypto_tao_network, so an agent can pick it without opening either schema.

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?

It gives explicit routing: use crypto_tao_subnet_validators for a single subnet's top validators by stake, and crypto_tao_network for fundamentals like block height and total issued. It also states the prerequisite (TAOSTATS_API_KEY) up front, so the agent knows the call will fail without credentials.

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