sap_list_connections

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the two host sources it spans (saplogon | sapguiserver) and the diagnostic meaning of a connection having no sessions with scripting_disabled=true.

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?

Front-loaded with the core action in the first sentence, followed by two short sentences that each add distinct value (coverage scope, diagnostic interpretation). No filler or restatement of the tool name.

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?

With zero parameters and an output schema present, the description does not need to enumerate return values. It supplies exactly the extra framing an agent needs: what is listed, which SAP clients are covered, and how to read the scripting_disabled condition.

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 tool takes zero input parameters, so the baseline is 4 and there is nothing to clarify on the input side. The host/scripting_disabled details in the description pertain to returned fields rather than parameters, and the output schema covers those returns.

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 opens with a specific verb and resource: 'List all open SAP connections and sessions,' and further scopes it to SAP Logon plus Business Client / embedded GUI sessions. It is clear what the tool returns, but it never names the nearest sibling (e.g. sap_get_session_info) to sharpen the boundary.

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?

Usage is only implied: an agent can infer this is the entry point for enumerating connections before calling session-level tools, and the final sentence gives a diagnostic interpretation. There is no explicit 'use this when' or 'use X instead' guidance naming alternatives such as sap_get_session_info.

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