Test RFC Connection

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

The description adds substantial behavioral context beyond the annotations: it discloses the dependency on node-rfc and the SAP NW RFC SDK, explains what happens if the SDK is missing, describes the JSON return shape, and clarifies that credentials are reused from environment variables. This gives an agent a realistic picture of the tool's runtime behavior and requirements.

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 concise and well-structured: purpose first, then dependencies, configuration, return shape, and bulleted notes. Every sentence adds relevant information with no fluff or repetition of schema or annotations.

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 simple read-only ping tool with one optional parameter and no output schema, the description is complete. It covers what the tool does, how to configure it, what it returns, credential handling, and the failure mode when the SDK is absent.

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 description coverage is 100%, and the single parameter response_format already has a full description and enum in the schema. The tool description adds no additional meaning to parameters, though it does mention a JSON return shape that is slightly inconsistent with the markdown/json response_format choice.

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 action ('Test the RFC connection to SAP') and the specific function module used (STFC_CONNECTION), making the tool's purpose unambiguous. However, it does not explicitly distinguish itself from the sibling tool 'sap_connection_test', which appears to serve a similar connectivity-checking purpose.

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 provides configuration prerequisites (direct vs. load-balanced connections) and notes about SDK installation, but it gives no guidance on when to use this tool versus alternative siblings like sap_connection_test or sap_rfc_system_info. There are no explicit exclusions or conditions for choosing this tool over others.

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