connect

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

With no annotations, the description carries the burden and discloses key behavior: it sets up both DevBridge and SSE connections and is a prerequisite for all other tools. It does not cover connection lifecycle details such as what happens on repeated calls or on failure, but for a connect operation it provides substantial useful context.

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?

Three efficiently ordered sentences: purpose first, then what connections are established, then the critical prerequisite and port guidance. Every sentence earns its place, and nothing is buried or redundant.

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 foundational connect tool with no output schema and full schema coverage, the description is complete enough. It covers purpose, dual connection behavior, prerequisite ordering, and how to obtain the port, leaving no essential gap for correct invocation.

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%, so the baseline is 3. The description adds meaning beyond the schema by specifying the default port (9001), the recommended source for the actual port from game stdout, and an example log line, which helps the agent supply the required port correctly.

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?

States a specific verb and resource: 'Connect to a game instance on a specific port (and optionally host).' It also explains the dual connection setup (DevBridge and SSE) and that it must be called before any other tools, clearly distinguishing it from sibling tools.

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?

Explicitly tells the agent when to use it: 'Must be called before using any other tools.' It also gives practical guidance for obtaining the correct port from stdout and notes the default port, covering both the prerequisite and the parameter acquisition path.

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