get_connection_status

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states that the tool returns connection and authentication status, which is the core behavior, but it does not elaborate on side effects (e.g., whether it's purely a read operation), error conditions, or the structure of the returned status. The behavior is not misleading, but the description is minimal.

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 very short and front-loaded, which is good. However, the 'Returns:' section is redundant with the first sentence ('Get current connection and authentication status' vs 'Current connection status'), wasting a line. It's concise but could be tighter by removing the duplication.

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?

The tool is simple with no parameters and an output schema is present, which reduces the need to describe return values. The description says enough to understand the basic purpose, but it lacks any contextual framing (e.g., when to use in the connection lifecycle relative to connect/login/disconnect). It's minimally complete but not enriched.

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 parameters, and the schema trivially covers this (100% coverage). According to the guidelines, a zero-parameter tool gets a baseline of 4, since the description cannot add parameter meaning beyond the empty schema. The description adds no param info, which is fine given there are none.

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 function: 'Get current connection and authentication status.' This distinguishes it from sibling tools like connect, disconnect, login, and logout by implying a read-only status check. However, it doesn't explicitly name those siblings, so it doesn't fully differentiate why it's not another status-like command.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, not the situations where it's appropriate (e.g., before trading, after connect or login). There are no exclusions or alternative tool references, leaving the agent to infer usage from the name and getter semantics.

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