system_ping

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

No annotations are provided, so the description is the only source of behavioral information. It discloses the expected return ('pong + TD frame'), and the 'canary' metaphor weakly implies a safe, non-mutating operation, but it doesn't explicitly state side-effect-free behavior or failure semantics.

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. The purpose and expected return are front-loaded, making it easy for the agent to parse quickly.

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 parameterless liveness check, the description is largely complete: it states the tool's purpose and its return value. It could be slightly stronger by explicitly noting the absence of side effects, but given the simplicity of the tool, this is minor.

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 has zero parameters and the schema fully covers that. The description adds no parameter explanation, but none is needed; nothing is left ambiguous.

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 uses a clear verb ('Returns') and identifies the tool as a liveness canary that returns 'pong + TD frame'. This conveys the core purpose well, though it doesn't explicitly differentiate it from sibling tools like system_info.

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 canary' phrasing implies it should be used for health/availability checks, but there is no explicit guidance on when to prefer this tool over alternatives, nor any exclusions. Context is present but minimal.

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