get_godot_version

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

The description indicates a safe read operation, consistent with no destructive side effects. However, it does not disclose where the version is fetched from, whether it might fail, or any additional behavior (e.g., caching, network access). With no annotations beyond the title, the description carries the full burden but omits these details.

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 extraneous words. It is front-loaded and efficient, perfectly fitting the tool's simplicity.

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 tool with no parameters, no output schema, and a simple purpose, the description is fully complete. It tells the agent exactly what the tool does without needing additional context.

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?

There are zero parameters, and the schema coverage is 100% (not applicable). The description does not need to add parameter information, and the lack of parameters is already clear from the input schema.

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 'Get the installed Godot version', which is a specific verb and resource. It is unambiguous and distinguishes itself from sibling tools, which are about editing, running, or managing projects.

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. While it is a simple getter, it does not mention typical use cases or prerequisites (e.g., requiring a Godot project to be open).

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