connect

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

No annotations are provided, so the description carries the behavioral burden. It discloses that this opens a TCP connection, performs a handshake, depends on KingstVIS running with the Socket API enabled, and supports environment-variable defaults. It does not mention idempotency or behavior when already connected, but the core side effect is clearly stated.

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 concise sentences, front-loads the primary action, and then gives the necessary configuration detail. Every sentence earns its place without redundancy.

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 connect operation with two optional parameters and no output schema, the description covers the main invocation concerns: default endpoint and runtime prerequisites. It does not describe the success/error response shape, but this is a minor gap given the tool's simplicity.

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 schema provides no descriptions (0% coverage), but the description compensates by explaining that empty host/port values fall back to KINGSTVIS_HOST/KINGSTVIS_PORT with default 127.0.0.1:23367. This adds real meaning beyond the raw schema properties.

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 uses a specific verb and resource: 'Open the TCP connection to KingstVIS and handshake'. It clearly conveys that this tool establishes a connection, distinguishing it from siblings like disconnect, get_status, and raw_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?

The description gives practical usage context: host/port can be left empty to use environment variables and a default address, and the software must be running with the Socket API enabled. It does not explicitly say when not to use it or mention alternatives, but the guidance is clear enough for a connection-establishment tool.

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