test_connection

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the shape of the result (version, edition, topology, auth user, transaction capability) in the absence of an output schema, though it says nothing about failure behavior when a connection is invalid.

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 dense sentence that front-loads the action and then enumerates the useful return fields with no filler or repetition.

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 no output schema the description does well to enumerate return content, but it leaves the sole input parameter entirely unexplained, which is the main thing an agent needs in order to actually invoke the tool correctly.

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?

There is one parameter ('connection', nullable, default null) at 0% schema description coverage, and the description never mentions it. It does not clarify whether the value is a connection name from list_connections, a URI, or what a null default selects, so the agent must guess.

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?

States a specific verb (connect) plus a detailed enumeration of what is returned: version, edition, topology, authenticated user, and transaction support. The resource and scope are unambiguous, but it never distinguishes itself from the sibling server_status, which plausibly overlaps.

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?

Usage is only implied by the tool name 'test_connection' and the diagnostic return payload; there is no explicit when-to-use statement, no mention of prerequisites, and no routing away from server_status at the point where an agent would most need it.

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