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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered; the description reinforces it redundantly but usefully adds the auth fact 'no key' and the behavioral filter that only networks with live data are returned. It stops short of saying anything about pagination or result ordering, which is the remaining gap.

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?

Four compact sentences, led by the purpose and follow-up routing, with no filler or marketing language. The 'Read-only, no key' clause partially duplicates the annotations, which is the only wasted space.

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?

All required parameters are optional and documented, an output schema exists so return values need no elaboration, and the description nonetheless names the returned fields (symbol, name, category, public page). An agent has everything needed to select and call this tool correctly.

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 100% and each of the three parameters (query, category, limit) is already documented, so the schema carries the load. The description's example tickers add a little flavor about query format, but it says nothing extra about category values or the limit default, so the baseline 3 applies.

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 (look up DePIN networks and Bittensor subnets), narrows the scope to entries with live data, and illustrates the input format with concrete tickers ('akash', 'helium', 'FIL'). It clearly differentiates itself from detail-oriented siblings like get_network by describing itself as the symbol-resolution step.

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 explicitly states the downstream purpose: 'Use it to get the symbol that get_network, get_metric_history and verify_value take.' That names three alternatives and the condition (need to resolve a symbol) that selects this tool over them, so the agent does not have to infer routing.

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