check_connection

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

No annotations are provided, so the description carries the full burden. It states 'Verifies connection,' which implies a read-only, non-destructive operation, but it does not disclose any behavioral details like error handling, latency, or side effects. The description is adequate for a simple health check but lacks depth.

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 concise sentence that is front-loaded with the key action and target. Every word serves a purpose, with no unnecessary information.

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?

Although the tool has no parameters and an output schema exists, the description does not mention what the output looks like or what constitutes a successful/failed connection. For a simple health check, this is adequate but could be improved by noting that it returns a status indicator.

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 input schema has zero parameters, so the description does not need to compensate for parameter documentation. As per guidelines, baseline score is 4 for tools with no parameters. The description does not add parameter semantics, which is acceptable.

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 purpose: 'Verifies connection to the backend Navidrome instance.' It uses a specific verb ('Verifies') and resource ('connection to the backend Navidrome instance'), which distinguishes it from sibling tools that focus on analysis, search, or playlist management.

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 usage context but does not provide explicit guidance on when to use this tool versus alternatives. It is clear that it is for verifying connectivity, but there is no mention of prerequisites, when not to use it, or references to sibling tools.

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