health_check

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Check' implying a read-only operation, but does not disclose specifics such as whether authentication is required, what exactly is checked (e.g., ping vs. full API test), or possible side effects. The description is too minimal to fully inform an AI agent of behavioral traits.

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: one short sentence that directly states the purpose. No filler or redundancy. Ideal length for this simple 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 simplicity (no parameters, clear purpose, and an output schema exists to define return values), the description is sufficiently complete. It covers the essential action and resource. However, it could benefit from a small note on when this check is useful (e.g., before other operations), but not strictly necessary.

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 no parameters, so the baseline is 4. The description adds no parameter-level information because none is needed. The input schema already provides full coverage (100%) with 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 tool's purpose: 'Check server health and API connectivity.' It uses a specific verb ('Check') and resource ('server health and API connectivity'), and is distinct from sibling tools which are all about data visualization and manipulation.

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 implies usage context (when you need to verify server status) but provides no explicit guidance on when or when not to use this tool versus alternatives. Sibling tools are unrelated, so no comparison is needed, but still lacks explicit usage boundaries.

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