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

The description discloses the exact SQL operation (SELECT 1), what it returns (server version + latency), and frames it as a lightweight alternative to describe_schema. Given readOnlyHint=true already in annotations, the description adds meaningful context about the tool's behavior without contradiction.

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 that is front-loaded with the core action and result. No redundant words; every phrase adds value, earning a top score.

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?

With one optional parameter, no required fields, and an output schema present, the description is complete enough. It describes the action, the use case, the alternative tool, and the return type (server version + latency), while the output schema handles detailed return structure.

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 description coverage is 100%, so the parameter 'connection' is already well-documented with guidance on resolution. The main description does not add additional parameter semantics beyond referencing 'a connection', thus a baseline score of 3 is appropriate.

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 function: 'Ping a connection (SELECT 1) and return server version + latency.' It uses a specific verb ('Ping') and resource ('connection') and distinguishes itself from describe_schema by positioning as a faster credential/network check.

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 explicitly indicates when to use this tool: 'Fast way to confirm credentials and network path without running describe_schema.' It also provides guidance in the schema to use list_connections for resolving the connection parameter, offering clear context and an explicit alternative.

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