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

With no annotations provided, the description carries the disclosure burden. It accurately describes the return value and echoes behavior. It does not mention side effects, but for a read-only liveness check this is adequate.

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?

Two concise sentences convey all necessary information with zero redundant text, perfectly front-loaded and efficient.

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 one-parameter utility with no output schema and no annotations, the description adequately conveys purpose, behavior, and parameter usage. It could mention error handling or lack of side effects, but these are not essential for a liveness probe.

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 already fully documents the optional message parameter with a clear description ('Optional message echoed back'). The tool description adds no new semantic meaning beyond confirming the echo, so a baseline 3 is appropriate per high schema coverage.

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's function as a 'Liveness probe' and specifies the output ('Returns pong plus any supplied message'). This specific verb+resource distinguishes it from the unrelated sibling tools.

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 liveness probe purpose clearly implies when to use it (e.g., connectivity checks), though it does not explicitly name alternatives or exclusions. Since no sibling tools are similar, the context is sufficient.

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