Check Godot Version

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

The readOnlyHint annotation already declares this as a read-only operation, and 'Check' is consistent with that. However, the description adds no extra behavioral detail beyond the annotation, such as what happens when godot_path is omitted or whether the tool errors on a missing executable.

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, short sentence without filler, which is structurally clean. However, it essentially restates the title and contributes little additional orienting information, so it is concise but not particularly value-adding.

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?

Given the tool's low complexity, full parameter schema coverage, an output schema, and a readOnlyHint annotation, the description is close to sufficient. Still, it omits when-to-use context and does not explain the behavior of the optional path parameter, which are small but real 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 sole parameter, godot_path, is fully documented in the input schema with the description 'Path to Godot executable' and a default of null, so schema coverage is 100%. The description itself adds no further meaning about how the path is resolved or used.

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 identifies the action ('Check') and the resource ('the Godot version'), so an agent can infer the basic operation. It does not explicitly differentiate from siblings, but 'version check' is distinct enough among the listed tools. Its near-verbatim repetition of the title keeps it from a top score.

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 no guidance on when to use this tool versus alternatives, and no context about scenarios where version checking is needed. It neither names related tools nor states exclusions, leaving usage entirely to inference.

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