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

The annotations already establish that this is a read-only operation, so the description's job is lighter. The description adds useful behavioral detail by stating the expected response ('pong') and the condition under which it is returned, though it does not discuss failure modes or timeout behavior.

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?

Three short sentences with the endpoint identity front-loaded, followed by return behavior and intended use. There is no redundant or filler text.

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 zero-parameter health-check tool with no output schema, the description supplies everything needed: what it is, what it returns, and when to call it. No additional output or parameter documentation is necessary.

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 no parameters, so there are no parameter semantics to explain. The schema is minimal and complete, and the description appropriately does not invent parameter details.

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 endpoint type (health check) and states exactly what it returns ('pong' when the THORNode is responding). This clearly distinguishes it from the many data-fetching sibling tools, which retrieve node or chain data rather than perform a liveness check.

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 explicitly says to use this tool to verify connectivity to the node, giving clear usage context. It does not name exclusions or alternative diagnostic tools, but the intended use is unambiguous for a zero-parameter health check.

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