health.ping

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

No annotations are provided, so the description must communicate behavioral traits. 'Health check' implies a read-only, safe operation, but it does not mention return value, latency, or potential side effects. For such a simple tool, the description is adequate but not proactive.

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 extremely concise: two words. Every word is necessary. It is front-loaded and contains no filler. While more detail could be added, the brevity is appropriate for a trivial health check tool.

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?

Given the tool's minimal complexity (no parameters, no output schema, no annotations), the description is complete. It fully informs the agent of the tool's function. No additional context is needed for an agent to use it correctly.

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, so the input schema covers everything. With 100% schema description coverage (no params to describe), the description does not need to add parameter details. The baseline of 4 is appropriate.

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 'Health check' clearly indicates the tool's purpose: to verify system availability. The name 'health.ping' reinforces this. It is distinct from sibling tools like 'plugin_repo.check_updates' which serve different functions.

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?

No explicit guidance on when to use this tool versus alternatives. However, the purpose is self-evident: it is a simple liveness check. The description does not clarify prerequisites or side effects, but given the zero-parameter nature, usage context is implied.

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