get_connection_status

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

With no annotations provided, the description carries the full behavioral burden and does so well by specifying the exact transports interrogated (Remote Control, Python, Plugin Bridge), which adds concrete disclosure beyond a generic status check. However, it does not describe edge cases like the behavior when no transports are connected or the return value shape, which would round out transparency for this zero-annotation scenario.

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 14-word sentence that front-loads the action and resource, with the parenthetical efficiently enumerating the specific transports. Every word earns its place; no wasted verbiage or irrelevant details.

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?

Given its low complexity (0 params, no schema, no annotations), the description covers the essential purpose fully, and the sibling list containing `sc_status` and `get_build_status` highlights how the explicit transport list helps disambiguate. However, it could note return value semantics (e.g., does it return a simple boolean, a list, etc.) since no output schema exists, which would make it fully complete.

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 tool has zero parameters, so the schema provides no room for ambiguity. Per the rubric, 0 parameters merits a baseline score of 4, and the description appropriately avoids inventing parameter details that don't exist.

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 ('Check') and resource ('Unreal Engine transports currently connected'), and lists the exact transports (Remote Control, Python, Plugin Bridge) that distinguish it from siblings like `get_build_status` and `sc_status`. The parenthetical adds precision without ambiguity, making its purpose immediately clear.

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 implies usage through its imperative 'Check' but provides no explicit guidance on when to use this tool versus alternatives, nor does it name any sibling for comparison. For a simple status-check tool, the usage context is fairly self-evident from the name and description, but the rubric's requirement for explicit when/when-not/alternatives is not met.

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