test_connection

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

The phrase 'does not affect existing connections' is a valuable behavioral disclosure, especially since no annotations are provided. Yet it omits details on return values, failure modes, or timeout behavior, leaving the description to carry the full transparency burden but only partially fulfilling it.

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 perfectly front-loaded with the core purpose. Every word earns its place, and it avoids unnecessary detail.

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 one-parameter tool with no output schema, the description adequately covers the tool's purpose and safety profile. It lacks explicit return/error semantics, but the simplicity of the tool makes the description reasonably complete for an agent to invoke it 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?

Schema coverage is 100%, with server_id already described as 'Server ID' in the input schema. The description adds no additional parameter meaning, so it does not go beyond what the schema already provides.

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 'Test server connectivity' with a specific verb+resource structure. The parenthetical 'does not affect existing connections' effectively distinguishes it from sibling tools like connect and disconnect, emphasizing its non-invasive nature.

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 this tool is for safe connectivity checks without side effects, which is useful context. However, it doesn't explicitly state when to use it over alternatives like connect or quick_connect, nor does it provide exclusion criteria.

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