healthcheck

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

No annotations are given, and the description fails to disclose behavioral traits such as idempotency, side effects, authentication requirements, or response behavior when the server is down. For a tool with no annotations, the description should carry the full burden, but it provides no such transparency.

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 a single sentence, which is concise, but it lacks structure or additional context. It earns its place by stating the purpose but does not go beyond the bare minimum, making it adequate but not well-crafted.

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 has no parameters and no output schema, the description should at least hint at the return value or behavior (e.g., status message, JSON object). It fails to do so, leaving the agent uninformed about what to expect after invocation.

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?

There are no parameters (schema coverage 100% by default), so according to the rules baseline is 4. The description adds no parameter meaning, but none is needed given zero parameters.

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 verb ('check') and resource ('server health and connectivity'), making the basic purpose unambiguous. However, it is somewhat generic and does not specify what 'health' entails or how it differs from similar tools, though sibling tools are mostly specific actions.

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 provided on when to use this tool versus alternatives (e.g., other connectivity checks). The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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