get_godot_version

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 only states 'Get the installed Godot version' and does not mention whether the operation is read-only, what happens if Godot is not installed, or any potential side effects. The verb 'Get' implies a read operation, but specific behavioral details are absent.

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 sentence with no filler or redundancy. It is highly concise and front-loaded, delivering the core action and object in just a few words, earning top marks for efficiency.

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 simplicity, the description is adequate in stating what it does, but with no output schema and no annotation, it does not disclose the return format or any edge-case behavior. For a trivial tool like this, it is minimally complete but leaves the exact return type unspecified.

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 schema coverage is trivially 100% with an empty properties object. Per the rubric, 0 parameters receives a baseline of 4, and the description does not need to explain anything further about parameters.

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 'Get the installed Godot version' uses a specific verb (Get) and resource (installed Godot version), unambiguously distinguishing it from siblings like launch_editor or test_run_scenario. The purpose is crystal clear and leaves no room for confusion.

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 or any contextual prerequisites. While the purpose implies it should be used to check the Godot version, there is no explicit 'use this when...' or 'instead of...' statement, leaving the agent without usage context.

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