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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds some context by listing example stats (sync status, version, latest block) but does not disclose error behavior, permission requirements, or the return format beyond what the output schema would provide. This is an acceptable but not rich disclosure.

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 description is a single, concise sentence fragment that is front-loaded with the key term 'Node software stats'. Every word adds value, and the ellipsis effectively signals that more examples exist without wasting space. It is appropriately sized for a simple tool.

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 low-complexity tool with one parameter, an output schema, and strong annotations, the description is minimally acceptable. It names the resource and gives examples of the data returned. However, it lacks usage guidance and parameter semantics, which are clear gaps given that the schema provides no descriptions. The annotations and output schema compensate for some of the missing context.

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 schema has 0% description coverage for the 'chain' parameter, and the description does not mention or explain the parameter at all. The only hints are the examples in the schema showing 'bitcoin' and 'ethereum', which imply the parameter is a blockchain identifier. The description fails to compensate for the missing parameter documentation, leaving the agent to infer semantics from the examples.

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 'Node software stats (sync status, version, latest block, …)' clearly identifies the tool as retrieving node-level statistics for a blockchain node. It specifies the resource (node software) and the type of data (sync status, version, latest block), distinguishing it from sibling tools like 'block' or 'transaction'. However, it lacks an explicit verb like 'get' or 'retrieve', which keeps it from being a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any specific use case, exclusions, or context where another tool would be preferred. With siblings like 'stats' and 'block', the absence of usage direction leaves the agent to infer applicability from the name and short description alone.

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