godot_generate_gut_test

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, idempotentHint=false) and offer no behavioral context. The description adds little beyond the word 'Scaffold' — it doesn't disclose whether an existing target file gets overwritten, what happens if GUT isn't installed, or whether the generated test is auto-run or merely created. For a file-writing tool this is a notable gap, though there's no contradiction with annotations.

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?

A single clear sentence with zero filler. The verb, resource, and target are all front-loaded and immediately actionable. No redundant restatement of the tool name or schema contents.

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 structurally simple with three documented parameters and an output schema present. However, for a scaffolding/write operation, an agent would benefit from knowing the overwrite behavior, dependency on the GUT addon, and whether the generated file is placed in a test directory convention. These gaps keep it from being fully complete, though the simplicity and existing schema prevent it from being inadequate.

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 input schema already documents all three parameters with useful descriptions (path to script, destination path, optional method list). Despite the 0% coverage signal, the visible schema carries the descriptive load. The tool description itself adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 specific verb ('Scaffold') with a clear resource ('GUT test script') and target ('class or script'). It distinguishes itself from the sibling godot_run_gut_tests, which executes tests rather than generating them, though it doesn't explicitly name that sibling. The purpose is unambiguous and identifiable.

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 gives no guidance on when to use this tool versus alternatives such as godot_run_gut_tests, godot_create_script, or godot_validate_script. No prerequisites (e.g., GUT must be installed as an addon) or exclusions are mentioned, leaving the agent to infer context.

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