toolhub.ping

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

With no annotations, the description carries the full behavioral burden, and it only implicitly conveys a read-only diagnostic intent via 'check'. It does not state side effects, auth requirements, or latency/rate behavior, but for a trivial ping the implied read-only nature is reasonably clear, especially since an output schema handles return values.

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?

A single front-loaded sentence with zero filler that states the purpose immediately. Nothing is wasted or repeated.

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 health-check tool with an output schema covering return values, the description is largely sufficient. The only gap is the unexplained 'message' parameter, which is minor given it is optional with a default.

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?

Schema coverage is 0%, so the description should compensate, yet it never mentions the single 'message' parameter (optional, default 'hello'). The one undocumented parameter is left with no semantic explanation in either the schema or the description.

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 states a specific verb (check) and resource (MCP ToolHub health/running state), which clearly reads as a health-check or liveness probe. It is distinguishable from siblings like toolhub.capabilities and toolhub.audit_recent, which serve different diagnostic purposes, though it does not explicitly name those alternatives.

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 guidance is given on when to use this tool versus the other toolhub diagnostic siblings (capabilities, audit_recent, request_status), nor any prerequisites or timing (e.g., before/after a call). Usage is left entirely to inference from the name.

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