control_join

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing: it does not say whether the call blocks until connected, what happens on a wrong password or unreachable host, whether it errors or retries, or what state change it causes. For a network-connection tool this is a significant transparency gap.

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?

A single front-loaded sentence with no filler and the core action stated first. It is efficient, though the extreme brevity borders on under-specification rather than tight writing.

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 no annotations, no output schema, and a genuinely stateful operation (establishing a server connection), the description should explain outcomes, failure behavior, and required preconditions. None of that is present, leaving the agent unable to predict what the call does or returns.

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% (ip, pass, and port all documented with defaults), so the schema already does the parameter work and a 3 is the baseline. The description adds only the indirect hint that a matchmade room may not need ip/port, without explaining that trade-off explicitly.

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?

"Connect to a game server" gives a specific verb (connect) plus resource (game server), and the parenthetical clarifies the two modes: LAN and matchmade room. It is clear on its own, but it never distinguishes itself from siblings such as control_lobby or control_start, which an agent could plausibly confuse with joining.

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: the mention of "LAN or a matchmade room" hints at two join scenarios, but there is no explicit when-to-use, no prerequisites (must you be authenticated, in a lobby, or have a room code first?), and no statement of when not to use it versus control_lobby or control_start.

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