Godot Runtime Status

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. It states what status is returned but gives no detail about whether it's a read-only query, whether it requires the project to be running, what failure states might occur (e.g., process not started), or what the return structure looks like. For a diagnostic/status tool this is a significant gap.

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 sentence, minimal waste. It says what it does in a compact way. Though it could add more value, there is no fluff or redundancy to penalize.

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 0 params and no output schema, the description should carry more contextual weight. It covers the basic purpose but omits what 'status' contains (bridge state, process alive/dead, PID, etc.), which would matter for an agent debugging a Godot project. The description is functional but leaves important interpretive gaps.

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 0 parameters, so there is nothing for the description to elaborate on. The baseline of 4 for zero-parameter tools applies — no param semantics are needed and none are expected.

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 verb 'Return' and resource 'runtime bridge and managed process status' give a reasonably clear purpose. However, it doesn't differentiate from siblings like godot_runtime_logs, godot_runtime_perf, and godot_editor_status — an agent could confuse what 'status' means here vs those other status/reporting tools.

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 vs alternatives. With six godot_runtime_* siblings and an editor_status tool, the agent receives no help distinguishing when to call this versus godot_editor_status or godot_runtime_perf. This is a zero-guidance description.

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