Godot Editor Status

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

No annotations are provided, so the description carries full responsibility. The description is simple and consistent with a read-only status check. It doesn't describe what the response looks like (boolean? text?), whether it can be called anytime, or whether it has side effects. But given the simplicity of a status check, the description is reasonably transparent — the agent can infer it's a non-destructive read operation.

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, complete sentence with zero wasted words. It states exactly what the tool does and nothing more. For a zero-parameter status check, this is ideal conciseness.

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, no-output-schema status check, the description is largely complete. The only gap is that it doesn't describe the return format, but with no output schema available, this could be helpful. However, given the overall simplicity of the tool, the description adequately conveys its purpose and is complete enough for an agent to invoke it correctly.

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 schema coverage is trivially 100%. With no parameters to document, there is nothing for the description to add. The baseline of 4 for a zero-param tool is appropriate here.

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 clearly states what the tool does: 'Check whether the Godot editor bridge is connected.' It uses a clear verb (Check) with a specific resource (Godot editor bridge connection status). It differentiates reasonably from siblings like godot_runtime_status (which checks runtime, not editor) and godot_project_info, though it doesn't explicitly name the distinction.

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?

There is no guidance on when to use this tool versus alternatives. No mention of whether it should be called before other editor operations, or how it differs from godot_runtime_status which checks the runtime connection. The distinction between 'editor bridge' and runtime status is implied by the sibling names but not stated.

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