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

With no annotations, the description carries the full behavioral burden. It does disclose a meaningful trait: the data comes from xmr.pub's self-hosted full node, which tells the agent about the source and trust boundary, and 'real-time' signals freshness. It says nothing about caching intervals, failure modes when the node is unreachable, or rate limits.

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 compact sentence, front-loaded with the resource ('Monero mainnet real-time status') and followed by a colon-delimited list of metrics, then a short provenance note. No filler; the only mild redundancy is listing fields that overlap with sibling tools.

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?

There is no output schema and no parameters, so the description is the only place return content can be conveyed — and it does enumerate the returned metrics, which is exactly what the agent needs. It falls short of 5 only because it omits error behavior and any indication of how the response is structured or how fresh the snapshot is guaranteed to be.

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 the baseline is 4. There are no inputs whose semantics could be clarified, and the description correctly focuses on what the call returns instead.

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 resource and scope: real-time Monero mainnet status, then enumerates the exact dimensions returned (height, sync state, difficulty/hashrate, mempool, chain DB size). That is far more than a restatement of the name. It only partially differentiates from the sibling xmr_mempool_health, since mempool is listed here as one of several metrics.

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?

Usage is implied by the word 'status' and the live-metric enumeration — an agent can infer this is a general node-health snapshot. However, there is no explicit when-to-use guidance and no routing against the overlapping siblings xmr_mempool_health or xmr_fee_oracle, which also surface network-level data.

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