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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — it does not state what a successful call returns (e.g., a status payload or empty response) or whether it requires connectivity/auth, which matters with no output schema to fill the gap.

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 words are as tight as possible and cannot be accused of padding, but this is under-specification rather than conciseness. There is no structure or front-loaded statement of what the call actually confirms.

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 read-only probe with no output schema, the description carries the burden of saying what the result means and when to invoke it. It does neither, and the presence of the near-synonymous sibling check_availability makes the omission consequential.

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 zero parameters, so there is no parameter semantics for the description to explain. Baseline 4 applies; nothing is missing on this dimension.

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?

"Health check" does convey more than the bare name "ping" — it tells the agent this is a liveness/status probe rather than a network ping. But it is a noun phrase with no verb and no scope, and it gives no basis for distinguishing it from the sibling check_availability, which an agent could easily confuse it with.

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 offers no when-to-use guidance, no prerequisites, and no exclusions. In particular it never says how this differs from check_availability, leaving the agent to guess between two plausibly overlapping probes.

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