get_ssh_connection_info

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

Since there are no annotations, the description must carry the behavioral burden. The description fails to specify if this is a safe, read-only operation, which is critical when no behavioral metadata is present and no input parameters are present.

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, focused sentence that explains the tool's function without any unnecessary filler, achieving maximum conciseness for a zero-parameter tool.

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 that there are zero parameters and no output schema to describe, the description is contextually complete regarding the function of the tool. It provides all the information necessary for an agent to decide if this is the correct tool to call.

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?

With zero parameters, the parameter semantics score is high. The description does not attempt to elaborate on non-existent parameters, relying on the clear purpose of the tool to convey that no input 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 is highly specific, naming the exact resource and required output: 'server SSH port and connection details.' This clearly differentiates it from other surrounding tools like get_server_info or get_ftp_port.

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 is a statement of function rather than a usage guide. While it clarifies what the tool does, it fails to explicitly guide the user on *when* to use it versus other similar connection-based tools in the environment.

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