test_connection

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

With no annotations, the description carries the full burden. It clearly states the tool tests the connection and checks OAuth status, implying a non-mutating diagnostic operation. It does not describe return values or failure behavior, but for a simple connectivity check this is largely sufficient.

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 two sentences and front-loads the main action. The second sentence is slightly redundant with the first ('Use this tool to check...' restates 'Test the connection'), but the overall structure is clear and efficient.

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, no-output-schema health check, the description provides sufficient context to understand the tool's purpose and when to use it. It lacks explicit return value details, but the simple nature of the operation makes this less critical.

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 are zero parameters, so the baseline is 4. The schema already has an empty properties object, and the description adds no parameter-specific detail because none is needed.

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 starts with 'Test the connection to SAP Datasphere', providing a specific verb ('Test') and resource ('connection'). It also adds 'verify OAuth authentication status', making the scope precise and distinguishing it from sibling tools like list_connections or datasphere_cli_status.

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?

It explicitly says 'Use this tool to check if the MCP server can successfully connect to SAP Datasphere', giving clear guidance on when to use it. However, it does not mention alternatives or exclusions, so it falls just short of a 5.

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