Status

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

No annotations are provided, so the description carries the full burden. It discloses what is inspected (ports, game/player, decompiler state), implying a non-mutating read, and it tells the agent to run it before other operations. It never explicitly states it is read-only/side-effect free, which is the one gap for a no-annotation tool.

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?

Two sentences, zero waste. The subject of the check is front-loaded and the usage instruction follows immediately; every clause adds information.

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 output schema and no annotations, the description compensates by enumerating the reported fields. It is complete enough to invoke correctly, though it omits any hint of response shape (e.g., per-instance list vs. summary) that an agent might want.

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 takes zero parameters, which is the baseline-4 case. There are no argument semantics to explain, and the description correctly implies a parameterless probe.

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 ('Check') and resource ('the connection') and enumerates exactly what is reported: live Roblox instances/Opiumware ports, the game/player per instance, and whether the decompiler is running. Among siblings (screenshot, execute, logs, scripts, network), it is unmistakably the diagnostic/health tool, so an agent can distinguish it without opening a schema.

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?

'Call this first or when something isn't working' gives explicit conditions for invocation, which is unusually useful for a diagnostic tool. It does not name a specific alternative tool to use instead, so it falls short of full when/when-not routing, but the trigger conditions are clear.

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