test_registry_connection

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

With no annotations present, the description carries the full burden of behavioral disclosure. It reveals the tool is legacy and less performant than the resource, but it doesn't say whether the operation is read-only, what a failed connection looks like, or what 'testing a connection' entails. This leaves material behavioral ambiguity.

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 compact: one sentence for the core function, plus a short compatibility note and a pointer to the preferred resource. Every sentence serves a purpose, and the most important caveat is front-loaded. No filler words.

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?

Given the absence of annotations, output schema, and any parameter documentation, the description is not sufficient on its own. It fails to mention return value/status semantics, registry parameter format, or error behavior. For a simple one-parameter tool, the gaps are still significant because there is no other documentation source.

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 schema has 0% description coverage, and the tool description only says 'a specific registry.' It doesn't explain the accepted format for the 'registry' parameter, what a null value does, or how it maps to a registry identifier. The description adds little beyond the parameter name itself.

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 states a clear verb and resource: 'Test connection to a specific registry.' It distinguishes itself from the sibling tool 'test_all_registries' by explicitly targeting one registry. The reference to the 'registry://status/{name}' resource further reinforces the per-registry scope.

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 warns that the tool is maintained only for backward compatibility and recommends using the 'registry://status/{name}' resource instead for better performance. This gives strong guidance against new usage, though it doesn't contrast with other siblings like 'ping' or 'get_registry_info'. Still, the main routing decision is made clear.

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