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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious behavior: a required TAOSTATS_API_KEY, an x402 pay-per-call cost of $0.005 USDC, and the fact that failed calls are not charged. What it omits is how output is shaped or paginated, though an output schema exists to carry that.

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 core capability and the sibling routing come first, followed by prerequisites and pricing; nothing is buried. The routing sentence is somewhat clunky and truncated ('into a specific', 'of a specific'), and the x402 payment detail is verbose, but all of it is decision-relevant for a paid tool.

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 read-only, output-schema-backed metric tool, the description covers purpose, prerequisites, cost, and alternatives, which is close to sufficient. The gap is that the advertised timeframe options are not reflected in the input schema, leaving ambiguity about how an agent selects 1h vs 30d.

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% and each of the four parameters (page, limit, hotkey, netuid) is documented with defaults and bounds, so the baseline is 3. The description adds no meaning about page/limit/hotkey/netuid semantics, and it advertises timeframes (1h, 1d, 7d, 30d APY) that have no corresponding schema parameter — a mismatch an agent may stumble on.

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 names a specific verb+resource combination: validator staking yield and APY breakdown for a specific Bittensor subnet, with timeframes and epoch participation rates. It also explicitly separates itself from crypto_tao_subnet_stake_flows (net flow) and crypto_tao_subnet_validators (top validators by stake), so an agent can route correctly without opening a 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 names two alternatives and states the exact condition that selects each ('when you need staked alpha trajectory and net flow' vs 'when you need top validators ... by stake'), which implicitly defines this tool's own lane: yield/APY over time. This is explicit when-to-use guidance with siblings, not just implied.

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