Nanites Ping

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

Because no annotations are provided, the description carries the full behavioral burden. It does disclose the tool's read-only nature implicitly through 'Liveness probe' and specifies the return content (server identity and transport health). It does not describe failure behavior, timeouts, or the exact shape of the response, but for a zero-parameter ping this is reasonably transparent.

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 two short sentences with no filler. It front-loads the core purpose ('Liveness probe') and immediately states what the caller receives, making it easy to scan and understand.

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 simple zero-parameter liveness check with no output schema, the description adequately explains the tool's purpose and high-level return values. It is not fully complete because it lacks detail on the exact response format and does not clarify how it differs from the overlapping `system_health_check` sibling, but the missing detail is not critical for invoking this tool.

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 input schema has zero properties, and schema description coverage is 100%, so there are no parameters to document. The description correctly needs to add nothing about parameters, matching the baseline for a zero-parameter tool.

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 clearly states the tool is a 'Liveness probe for the Nanites MCP server' and that it 'Returns server identity and transport health.' This gives a specific verb and resource. However, it does not explicitly distinguish itself from the similarly-named sibling `system_health_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?

The phrase 'Liveness probe' strongly implies this tool is used to check whether the server is alive and healthy. However, there is no explicit guidance about when to prefer this over sibling tools like `system_health_check`, and no exclusions or alternative usage instructions are provided.

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