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

With no annotations, the description must carry the behavioral load. It usefully discloses that no API key is required and that subnet data is out of scope, but says nothing about caching, freshness, rate limits, or failure behavior. Output schema exists, so return-shape disclosure is not expected.

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?

Two short fragments, zero filler, with the scope statement front-loaded. It is terse to the point of being cryptic, and mixing Czech with English technical terms adds a small comprehension cost.

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 zero-parameter read tool with an output schema, the essentials are present: what it returns, the no-key requirement, and the subnet-data exclusion. It stops short of stating read-only/non-destructive behavior and freshness expectations, which the absent annotations would otherwise have to cover.

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 there is no parameter semantics to explain; the baseline for a 0-param tool applies. Schema description coverage is 100%.

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 resource and scope: Bittensor network liveness, and enumerates what it surfaces (peers, head block). That is more concrete than the bare tool name. It does not, however, differentiate itself from health-adjacent siblings such as get_execution_health or get_agent_liveness.

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?

"Bez klíče — žádná subnety data" implies a credential-free call and excludes subnet-level data, which gives the agent some routing signal. It never names an alternative tool or states positively when this tool should be chosen over the sibling health/reputation tools.

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