babylonjs_connection_status

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

No annotations are provided, so the description carries the behavioral disclosure burden. It transparently describes a read-only status operation and lists what will be returned: browser connection state, engine type, rendering capabilities, and available tool categories. It could explicitly state that it has no side effects, but for a status probe this is reasonably clear.

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 front-loaded sentence with no filler. It opens with the action, names the target, and compactly lists the return areas, making every phrase useful.

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 zero-parameter status probe with no output schema, the description is nearly complete: it states the action and the high-level return contents. It could name the specific tool categories available, but that is an enhancement rather than a necessary fix.

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 and the input schema is empty, so the schema already covers everything needed. With no parameters to document, the description does not need to compensate for any parameter gaps.

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 states a specific verb, 'Check', and a specific resource, 'current connection state of the BabylonJS inspector'. It also enumerates the returned contents, which clearly distinguishes it from the sibling action-oriented tools like babylonjs_scene_inspect and babylonjs_screenshot.

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 intended use is implied: check connection state before using inspector tools. However, the description does not explicitly say when to use it versus alternatives or name any exclusions, so the agent must infer the usage context from the tool name and sibling list.

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