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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the required TAOSTATS_API_KEY, the paid access model ($0.002 USDC per successful call via x402 on Base, Solana, or Arc), and that failed calls are not charged. That cost-and-auth information directly affects an agent's decision to invoke the tool.

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?

Front-loaded with the core purpose, then auth, then alternatives, then pricing — a sensible order. Minor waste in the phrasing 'Related tools on this server, for a different need:' and a stray capitalized 'Detailed', but no substantive bloat.

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?

With zero parameters and an output schema covering return values, the remaining agent-facing unknowns are auth and cost — both documented. Nothing needed to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no filtering by saying results cover all active pools.

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?

States a specific resource and scope: spot price in TAO, pool liquidity, and reserve balances for all active Bittensor dTAO subnet pools. It also explicitly distinguishes itself from crypto_tao_alpha_price_history (historical) and crypto_tao_subnet (single subnet), so an agent can route without opening schemas.

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?

Names two alternatives and the exact condition that selects each: history tool for historical price trajectory, subnet tool for single-subnet detail. The implicit condition for this tool (current snapshot across all pools) is clear from the contrast.

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