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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety and idempotency profile is fully covered. The description adds that the values reflect 'current' network state and lists the four fields, but says nothing about freshness/lag, units, or whether mempool size is transaction count or bytes.

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?

A single front-loaded sentence with the resource stated first and the returned metrics enumerated after the colon. No filler, no redundancy, and the most important information leads.

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, the description carries the burden of describing return values and does so by naming all four metrics. The remaining gap is that units and formats (e.g., hashrate denomination, whether height reflects indexer lag) are unspecified, which matters for a metrics tool with no structured output definition.

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 meaning to convey; the baseline for a no-argument tool applies. The description correctly signals a parameterless snapshot call, leaving nothing for the schema to contradict.

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 (Monero network state) and enumerates the metrics returned: indexed height, difficulty, hashrate, and mempool size. It does not, however, distinguish itself from siblings like network_hashrate, network_mempool, or network_blocktime, which cover overlapping data, so an agent cannot tell purely from the text whether to use this aggregate tool or the narrower ones.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only implicit signal is the word 'Current', suggesting a live snapshot rather than historical analysis, but an agent must infer that this is the aggregate entry point versus the per-metric tools.

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