godot_connect

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions WebSocket as the transport, it fails to disclose critical behavioral traits: connection persistence, failure modes (throws vs returns false), authentication requirements, or whether this establishes global state for subsequent tool calls.

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 a single, efficient sentence with no redundant or wasteful text. It is appropriately front-loaded with the core action. However, given the lack of annotations and schema documentation, it is arguably too terse rather than appropriately sized.

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 connection primitive with no annotations, no output schema, and zero schema coverage, the description is insufficient. It lacks critical operational context such as error handling behavior, connection lifecycle management, and the fact that this likely must be called before other Godot tools can function.

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 input schema has 0% description coverage for the 'timeoutMs' parameter. The description makes no mention of this parameter or its purpose (WebSocket connection timeout), failing to compensate for the undocumented schema. It neither explains the default value nor the minimum constraint.

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 provides a specific verb ('Connect') and resource ('running Godot bridge'), along with the protocol ('WebSocket'). It effectively distinguishes from sibling tools like 'godot_disconnect' and 'godot_status' through the clear action verb, though it doesn't explicitly reference those relationships in the text.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., that Godot must be running) or the relationship to 'godot_disconnect'. It fails to indicate whether this should be called before other Godot tools.

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