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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one real trait — that the comparison is against a cached sample, implying staleness and a fixed sampling interval — but it omits units, how old the cache is, whether a missing or first-run sample causes an error, and the shape of the result.

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 single fragment is efficient with no wasted words, but it is under-specified rather than concise in a useful way — it reads as a label, not a front-loaded explanation. A verb-led sentence stating the returned delta would cost no more length and communicate far more.

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 no output schema, no annotations, and no parameters, the description is the only source of information about the return value, and it does not supply it. Units, delta versus absolute value, cache age, and first-call behavior are all left unknown, which is a significant gap for an otherwise trivially simple tool.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter gaps exist to penalize.

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 phrase 'Network hashrate versus the previous cached sample' does convey the resource (network hashrate) and the comparison basis (prior cached sample), which is more than a restatement of 'get_hashrate_shift'. However, it is a noun fragment rather than a statement of what the tool returns or does, and it never clarifies whether the result is an absolute value, a delta, or a percentage. No sibling tool covers hashrate, so there is nothing to differentiate against.

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?

There is no guidance on when to call this tool, what question it answers, or what alternative to use for related network metrics. An agent must infer the use case entirely from the name and the four-word fragment.

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