healthcheck

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions checking 'health and connectivity' but fails to specify what metrics are evaluated (e.g., uptime, response time, error rates), whether it performs active tests or passive checks, or what the output format might be. This leaves critical behavioral traits unclear.

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, efficient sentence with no wasted words, front-loading the core purpose ('Check server health and connectivity'). It achieves maximum clarity in minimal space, making it easy for an 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?

Given the tool's simplicity (no parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'health' entails, how results are returned, or any prerequisites (e.g., authentication). For a diagnostic tool in a complex server environment, more context is needed to ensure effective use.

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 input schema has 100% description coverage (though empty). The description appropriately doesn't waste space on parameter details, aligning with the schema's completeness. A baseline of 4 is justified as no parameter information is needed or missing.

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 tool's purpose with a specific verb ('Check') and resource ('server health and connectivity'), making it immediately understandable. However, it doesn't differentiate from potential sibling tools like 'tracesList' or 'debuggerAttach' that might also assess system status, leaving room for ambiguity in a crowded toolset.

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 provides no guidance on when to use this tool versus alternatives, such as during system diagnostics, pre-operation checks, or error troubleshooting. In a server with over 100 sibling tools, this lack of context makes it hard for an agent to determine optimal usage scenarios.

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