game_connect_signal

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

Annotations are minimal (only title). Description implies mutation ('connect in running game') but doesn't disclose side effects (e.g., if connection already exists, reversibility, required node states). With low annotation coverage, description should provide more behavioral 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?

Single sentence, no unnecessary words. Front-loaded with action and context. Efficient.

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?

No output schema, no return value info. Description lacks details on error cases or post-connection behavior. For a 4-param mutation tool, it's adequate but not thorough.

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 has 100% parameter description coverage, so description need not add extra meaning. The tool description does not elaborate on parameters beyond schema, but schema itself is adequate. Baseline 3 is appropriate.

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?

Description clearly states the action (connect), resources (signal, node, method), and context (running game). Distinguishes from siblings like game_disconnect_signal and game_emit_signal.

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 on when to use this tool versus alternatives like game_disconnect_signal or game_emit_signal. Missing prerequisites or context about when connection is valid.

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