Ping

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

Despite having no annotations, the description explains what the tool does—performs a health check (likely non-destructive) and optionally verifies ClickHouse connectivity, meaning it may make an external connection. It does not fully disclose potential error conditions or timeout behavior, but for a simple health check this coverage is sufficient and accurate.

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, clear sentence with no filler. It front-front loads the primary purpose (health check) and optional connectivity check, making it easy to parse.

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?

The tool is simple (no parameters), has a schema, and an output schema exists. The description covers its essential function and optional behavior, leaving no meaningful information an agent would need to invoke it successfully.

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?

This tool accepts zero parameters, and the schema is empty (100% coverage trivially). No parameter explanation is required from the description. Baseline 4 applies since no parameters exist.

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?

Description clearly states a specific action ('health check') and resource ('MCP alive; optionally verifies ClickHouse connectivity'). It distinguishes itself from sibling tools like query_clickhouse and list_allowed_tables by focusing on liveness, not data access.

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 gives clear context about when this tool is appropriate (to check if the MCP server is alive and optionally ClickHouse connection). It does not explicitly mention alternatives or exclusions, but the purpose is self-evident as a diagnostic tool and the sibling tools are obviously different in scope. This meets the 'clear context, no exclusions' criterion.

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