godot_list_instances

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

The description claims a listing/read-only operation, but the annotations have readOnlyHint=false and idempotentHint=false, directly contradicting the implied behavior. This is a serious inconsistency that could mislead an agent about the tool's side effects and safety.

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, efficient sentence that front-loads the action and resource. It conveys the essential information without any fluff.

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?

The tool is simple with no parameters and no output schema, so the description's coverage of purpose and the environment prerequisite is adequate in isolation. However, the behavioral contradiction with annotations leaves a significant gap in understanding, preventing a higher completion score.

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, and the schema coverage is 100% (empty). The description adds output field context (id/project/port/status), which is useful for understanding the result. The zero-parameter baseline is 4, and there are no parameter semantics to clarify.

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 the specific verb '列出' (list) with a clear resource '所有发现的 Godot 实例' (all discovered Godot instances), and additionally specifies the output fields (id/project/port/status). This distinguishes it from siblings like godot_select_instance, which selects rather than enumerates.

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 provides a precondition: it requires GODOT_MCP_MULTI_INSTANCE=true, which tells the agent when this tool can be invoked. However, it does not explicitly state when to prefer this tool over alternatives like godot_select_instance or godot_list_dynamic_routes, nor does it mention when not to use it.

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