mysql_ping

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

With no annotations provided, the description carries the full burden. It discloses that this is a reachability check and what it returns, which implicitly signals a non-destructive, read-only operation. It doesn't elaborate on failure modes or authentication needs, but for a simple ping tool this is reasonable 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?

A single, front-loaded sentence communicates the action, target, and return values with no filler. Every word is informative and the structure makes it easy for an agent to quickly understand the tool's purpose.

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?

For a zero-parameter utility with an output schema, the description is complete: it states the connectivity check and the specific return fields. The sibling context makes it clear this is part of a MySQL diagnostic family, and nothing critical is missing.

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 schema coverage is 100%, so the baseline of 4 applies. The description adds no parameter-specific detail because there are none, but it does provide useful context about what the tool returns, which goes slightly beyond the empty schema.

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 states a specific verb 'Check' and a clear resource 'SSH + MySQL reachability', then explicitly lists the returned information: version, hostname, and server time. This clearly distinguishes it from sibling tools that inspect process lists, queries, status variables, and other MySQL diagnostics.

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 clearly implies the tool is for verifying SSH and MySQL connectivity, which is a natural precursor to deeper diagnostics. It doesn't explicitly name alternatives or exclusion conditions, but the intended usage context is obvious from the wording and the sibling tool set.

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