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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description adds meaningful behavioral context: name data is untrusted/self-reported for unverified nodes, IP addresses and cities are never published, and propagation delay is omitted when it was not timed. These are real caveats an agent needs, though no pagination or rate-limit behavior is mentioned.

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?

It is a dense run-on paragraph, but every clause earns its place by documenting returned fields that have no output schema to carry them, and the filter semantics are front-loaded. Slightly heavy nesting of field lists costs it a point.

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 appropriately carries the return-shape burden and covers filters, trust caveats and privacy constraints. It is effectively complete for invoking the tool, though it says nothing about ordering, limits, or truncation of the node list.

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 already 100%, so the baseline is 3, but the description adds default-state semantics the schema omits: offline nodes are filtered out unless include_offline=true, and verified_only keeps operator-verified nodes only. This clarifies the consequence of omitting each flag rather than merely restating it.

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 (the nodes reporting to the status page) and enumerates the exact fields returned, making it distinguishable from siblings like network_health, mining_stats or network_propagation. It never frames the action as a verb ('list'), but the scope and content are unambiguous.

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 gives clear context on filtering behavior (offline nodes are excluded by default unless include_offline=true; verified_only=true keeps only verified nodes) and a scope boundary ('the nodes that report to it, not every node on the network'). However, no alternative or sibling tool is named for the cases where this dataset is the wrong one.

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