godot_run_gut_tests

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

The description adds little beyond the annotations: it says 'capture test results' but does not explain potential side effects of executing test scripts, how tests are discovered, whether a GUT plugin is required, or what meaningful difference exists beyond the default readOnlyHint=false and idempotentHint=false.

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 extremely concise and contains no filler or repetition. It states the core action and outcome in a single efficient sentence.

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 that runs GUT tests and can produce side effects, the description is too thin. It omits prerequisites, expected project state, how it differs from godot_run_tests, and how the agent should choose between directory-wide and single-file test execution.

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 description contributes no parameter-level explanation, but the input schema documents prefix, test_dir, test_file, extra_args, and config_file with defaults and examples. Since the schema carries the parameter meaning, this is an adequate but not exceptional baseline.

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 a clear verb and resource: 'Execute GUT test suites and capture test results.' It distinguishes the tool from generic test runners like godot_run_tests by naming GUT specifically, though it does not explicitly contrast itself with sibling 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 about when to use this tool versus godot_run_tests, when to use godot_generate_gut_test, or what prerequisites apply. The only implied use case is 'run GUT tests,' which an agent could already infer from the tool name.

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